This is an automated email from the ASF dual-hosted git repository.
rusackas pushed a change to branch chore/react-resize-detector-upgrade
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 105dc0b14f chore(deps): upgrade react-resize-detector to v9.1.1
add b71654877f chore(deps-dev): bump @types/node from 25.2.0 to 25.2.1 in
/superset-websocket (#37719)
add 1c35c3f6d0 chore(deps): bump markdown-to-jsx from 9.7.2 to 9.7.3 in
/superset-frontend (#37730)
add 9b861b2848 chore(deps): bump caniuse-lite from 1.0.30001768 to
1.0.30001769 in /docs (#37726)
add c362bd2cac chore(deps): upgrade react-resize-detector to v9.1.1
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (105dc0b14f)
\
N -- N -- N refs/heads/chore/react-resize-detector-upgrade
(c362bd2cac)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
docs/package.json | 2 +-
docs/yarn.lock | 8 ++++----
superset-frontend/package-lock.json | 8 ++++----
superset-frontend/package.json | 2 +-
superset-websocket/package-lock.json | 14 +++++++-------
superset-websocket/package.json | 2 +-
6 files changed, 18 insertions(+), 18 deletions(-)
