This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/superset-frontend/npm-11.9.0
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 92d9c477827 chore(deps-dev): bump npm from 11.5.2 to 11.9.0 in
/superset-frontend
add 246dbd7f5c0 chore(deps): upgrade react-resize-detector to v9.1.1
(#37741)
add c7a62db0166 chore(deps-dev): bump npm from 11.5.2 to 11.9.0 in
/superset-frontend
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 (92d9c477827)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/npm-11.9.0 (c7a62db0166)
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 | 3833 ++++++++++++++++++-----------------
superset-frontend/package-lock.json | 21 +-
superset-frontend/package.json | 2 +-
4 files changed, 1938 insertions(+), 1920 deletions(-)
