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/wait-on-9.0.4
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 1c07f8d236e chore(deps-dev): bump wait-on from 9.0.3 to 9.0.4 in
/superset-frontend
add d748ed19ced chore(deps): bump hot-shots from 13.2.0 to 14.0.0 in
/superset-websocket (#37993)
add 232b34d9443 chore(deps-dev): bump webpack-sources from 3.3.3 to 3.3.4
in /superset-frontend (#38004)
add eee3af57759 chore(deps-dev): bump oxlint from 1.46.0 to 1.47.0 in
/superset-frontend (#38005)
add 982e2c1ef7f chore(deps-dev): bump webpack from 5.105.0 to 5.105.2 in
/superset-frontend (#38003)
add 999fa8cf3fb chore(deps-dev): bump wait-on from 9.0.3 to 9.0.4 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 (1c07f8d236e)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/wait-on-9.0.4 (999fa8cf3fb)
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 | 176 +++++++++++++++++------------------
superset-frontend/package.json | 6 +-
superset-websocket/package-lock.json | 14 +--
superset-websocket/package.json | 2 +-
4 files changed, 99 insertions(+), 99 deletions(-)
