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/multi-5aecdf029b
in repository https://gitbox.apache.org/repos/asf/superset.git
omit f99ea95f2a chore(deps-dev): bump jest and @types/jest in
/superset-frontend
add ae090fa74c chore(deps-dev): update @types/prop-types requirement from
^15.7.2 to ^15.7.15 in /superset-frontend/packages/superset-ui-core (#34451)
add 486b0122d0 chore(deps-dev): update jest requirement from ^30.0.4 to
^30.0.5 in /superset-frontend/plugins/plugin-chart-pivot-table (#34462)
add 923b2b1d77 chore(deps-dev): bump @babel/runtime-corejs3 from 7.26.7 to
7.28.2 in /superset-frontend (#34464)
add ecd22e8f54 chore(deps-dev): bump jest and @types/jest 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 (f99ea95f2a)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/multi-5aecdf029b
(ecd22e8f54)
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 | 2119 +++-----------------
superset-frontend/package.json | 2 +-
.../packages/superset-ui-core/package.json | 2 +-
3 files changed, 247 insertions(+), 1876 deletions(-)
