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/packages/superset-ui-demo/fork-ts-checker-webpack-plugin-tw-9.1.0
in repository https://gitbox.apache.org/repos/asf/superset.git


 discard 22165fe9d5 chore(deps-dev): update fork-ts-checker-webpack-plugin 
requirement
     add e03d840d06 chore(deps-dev): bump @babel/preset-env from 7.26.7 to 
7.27.2 in /superset-frontend (#33499)
     add e520538af6 chore(deps): bump antd from 5.24.9 to 5.25.1 in /docs 
(#33490)
     add 0f240ea1b2 chore(deps-dev): bump webpack from 5.99.7 to 5.99.8 in 
/docs (#33492)
     add 6da7759552 chore(deps-dev): update fork-ts-checker-webpack-plugin 
requirement

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   (22165fe9d5)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/superset-frontend/packages/superset-ui-demo/fork-ts-checker-webpack-plugin-tw-9.1.0
 (6da7759552)

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                                     |  46 +-
 superset-frontend/package-lock.json                | 840 ++++++++++-----------
 superset-frontend/package.json                     |   2 +-
 .../packages/superset-ui-demo/package.json         |   2 +-
 5 files changed, 435 insertions(+), 459 deletions(-)

Reply via email to