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/babel/types-7.29.0
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 4ffd49f3fe2 chore(deps-dev): bump @babel/types in /superset-frontend
add 32ee160c75e chore: Properly untrack WebSocket config file for docker
(#37624)
add 0d7cc88b2bd chore(deps): bump antd from 6.2.2 to 6.2.3 in /docs
(#37629)
add 601fcb3382d chore(deps-dev): bump @babel/preset-env from 7.28.6 to
7.29.0 in /superset-frontend (#37635)
add d7719e1a72a chore(deps-dev): bump @babel/types 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 (4ffd49f3fe2)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/babel/types-7.29.0
(d7719e1a72a)
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:
UPDATING.md | 15 ++
docker/superset-websocket/config.json | 22 ---
docs/package.json | 2 +-
docs/yarn.lock | 52 +++---
superset-frontend/package-lock.json | 180 +++++++++++----------
superset-frontend/package.json | 2 +-
.../packages/superset-core/package.json | 2 +-
.../packages/superset-ui-demo/package.json | 2 +-
8 files changed, 142 insertions(+), 135 deletions(-)
delete mode 100644 docker/superset-websocket/config.json
