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 aa58fe78943 chore(deps-dev): bump npm from 11.5.2 to 11.9.0 in
/superset-frontend
add ddba88ffada chore(deps): bump googleapis from 171.2.0 to 171.4.0 in
/superset-frontend (#37736)
add 7d9a8a0c5a4 chore(deps-dev): bump @babel/node from 7.28.6 to 7.29.0 in
/superset-frontend (#37734)
add 87d15d32c46 chore(deps-dev): bump @types/node from 25.2.0 to 25.2.1 in
/superset-frontend (#37732)
add e3a8ac2e190 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 (aa58fe78943)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/npm-11.9.0 (e3a8ac2e190)
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:
superset-frontend/package-lock.json | 28 +++++++++++-----------
superset-frontend/package.json | 6 ++---
.../packages/superset-ui-core/package.json | 2 +-
3 files changed, 18 insertions(+), 18 deletions(-)
