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


 discard 05f77eb  build(deps): bump react-select from 3.1.0 to 4.3.0 in 
/superset-frontend
     add 8e6803f  chore: Bumping lodash version in Superset (#14203)
     add 86d2a61  fix(emotion): add separate namespace for menu app (#14362)
     add 325dd62  build(deps): bump react-select from 3.1.0 to 4.3.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   (05f77eb)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/superset-frontend/react-select-4.3.0 
(325dd62)

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  | 588 +++++++----------------------------
 superset-frontend/package.json       |   5 +-
 superset-frontend/src/views/menu.tsx |  19 +-
 3 files changed, 128 insertions(+), 484 deletions(-)

Reply via email to