This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/docs/swc/core-1.15.18
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 0500ec56663 chore(deps): bump @swc/core from 1.15.17 to 1.15.18 in
/docs
add 00c62cf8203 chore(deps-dev): bump yeoman-test from 11.2.0 to 11.3.1 in
/superset-frontend (#38326)
add d738431e73e chore(deps): bump swagger-ui-react from 5.31.2 to 5.32.0
in /docs (#38324)
add 23200e8ce97 chore(deps): bump caniuse-lite from 1.0.30001774 to
1.0.30001775 in /docs (#38322)
add adc5a2cbdb6 chore(deps-dev): bump globals from 17.3.0 to 17.4.0 in
/superset-websocket (#38321)
add 00a14877059 chore(deps): bump hot-shots from 14.0.0 to 14.1.1 in
/superset-websocket (#38320)
add 33d2809f487 chore(deps): bump @swc/core from 1.15.17 to 1.15.18 in
/docs
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 (0500ec56663)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/docs/swc/core-1.15.18 (33d2809f487)
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 | 4 +-
docs/yarn.lock | 569 +++++++++++----------
superset-frontend/package-lock.json | 307 ++++++++---
.../packages/generator-superset/package.json | 2 +-
superset-websocket/package-lock.json | 28 +-
superset-websocket/package.json | 4 +-
6 files changed, 567 insertions(+), 347 deletions(-)
