This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot/npm_and_yarn/airflow-core/src/airflow/ui/core-ui-package-updates-9e843267bf
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard a91a7ac488b Bump the core-ui-package-updates group across 1 directory 
with 55 updates
     add 41594f73f47 Upgrade Happy-Dom in Plugin Template as well (#57287)
     add 55a3a64e8bb Bump vite from 7.1.7 to 7.1.11 in 
/providers/edge3/src/airflow/providers/edge3/plugins/www (#56909)
     add 932742e474f Bump the core-ui-package-updates group across 1 directory 
with 55 updates

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   (a91a7ac488b)
            \
             N -- N -- N   
refs/heads/dependabot/npm_and_yarn/airflow-core/src/airflow/ui/core-ui-package-updates-9e843267bf
 (932742e474f)

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:
 .../react_plugin_template/package.json             |   2 +-
 .../react_plugin_template/pnpm-lock.yaml           |  43 +-
 .../providers/edge3/plugins/www/package.json       |   2 +-
 .../providers/edge3/plugins/www/pnpm-lock.yaml     | 444 ++++++++++-----------
 providers/edge3/www-hash.txt                       |   2 +-
 5 files changed, 250 insertions(+), 243 deletions(-)

Reply via email to