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/npm-11.8.0
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard a411b4e510 chore(deps-dev): bump npm from 11.5.2 to 11.8.0 in 
/superset-frontend
     add 7c69ec7f24 chore(deps): bump markdown-to-jsx from 7.7.4 to 9.6.0 in 
/superset-frontend (#37354)
     add 790b79541b chore(deps-dev): bump globals from 17.0.0 to 17.1.0 in 
/superset-websocket (#37380)
     add 6a46700721 chore(deps): bump caniuse-lite from 1.0.30001765 to 
1.0.30001766 in /docs (#37381)
     add eeb4065d7d chore(deps): bump unist-util-visit from 5.0.0 to 5.1.0 in 
/docs (#37383)
     add beaa3d1f3f chore(deps-dev): bump npm from 11.5.2 to 11.8.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   (a411b4e510)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/superset-frontend/npm-11.8.0 (beaa3d1f3f)

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                       | 16 ++++++-------
 superset-frontend/package-lock.json  | 45 +++++++++++++++++++++++++++++++-----
 superset-frontend/package.json       |  2 +-
 superset-websocket/package-lock.json | 14 +++++------
 superset-websocket/package.json      |  2 +-
 6 files changed, 58 insertions(+), 25 deletions(-)

Reply via email to