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/eslint-10.0.0
in repository https://gitbox.apache.org/repos/asf/superset.git
discard 242d0c27c2f chore(deps-dev): bump eslint from 8.57.1 to 10.0.0 in
/superset-frontend
add af3e0882331 build(deps): resolve GHSA-36jr-mh4h-2g58 by upgrading
d3-color to 3.1.0 (#37981)
add 925a8457303 chore(deps-dev): bump eslint from 8.57.1 to 10.0.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 (242d0c27c2f)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/superset-frontend/eslint-10.0.0 (925a8457303)
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 | 581 +++++++--------------
superset-frontend/package.json | 5 +-
.../legacy-plugin-chart-horizon/package.json | 2 +-
.../legacy-preset-chart-deckgl/package.json | 4 +-
.../plugins/plugin-chart-word-cloud/package.json | 2 +-
5 files changed, 199 insertions(+), 395 deletions(-)
