This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/npm_and_yarn/airflow-core/src/airflow/ui/v3-3-test/3-3-core-ui-package-updates-7b07f53b1f
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit f3d2a2185b2 Bump the 3-3-core-ui-package-updates group across 1
directory with 4 updates
add 0d3616123e0 Bump the 3-3-uv-dependency-updates group in /dev/breeze
with 4 updates (#70853)
add 1fd40eae5a7 Bump the 3-3-auth-ui-package-updates group across 1
directory with 2 updates (#70851)
add 8ecaf1718e4 Bump the 3-3-core-ui-package-updates group across 1
directory with 4 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 (f3d2a2185b2)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airflow-core/src/airflow/ui/v3-3-test/3-3-core-ui-package-updates-7b07f53b1f
(8ecaf1718e4)
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:
.../auth/managers/simple/ui/package.json | 4 +-
.../auth/managers/simple/ui/pnpm-lock.yaml | 272 +++++++++++----------
dev/breeze/uv.lock | 60 ++---
3 files changed, 177 insertions(+), 159 deletions(-)
