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/v3-1-test/core-ui-package-updates-35c933d1fa
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard b456a884865 Bump the core-ui-package-updates group across 1 directory
with 57 updates
add fc19a7c9cff [v3-1-test] Bump glob from 10.4.5 to 10.5.0 in
/airflow-core/src/airflow/api_fastapi/auth/managers/simple/ui (#58443) (#58463)
add 648cea0c239 [v3-1-test] Minor updates to the python client release
guide (#58442) (#58465)
add 35ef3f0cfe2 [v3-1-test] Remove leftover reference to glob 10.4.5
(#58467) (#58468)
add a5ab871cea3 Bump the core-ui-package-updates group across 1 directory
with 57 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 (b456a884865)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airflow-core/src/airflow/ui/v3-1-test/core-ui-package-updates-35c933d1fa
(a5ab871cea3)
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:
.../api_fastapi/auth/managers/simple/ui/package-lock.json | 7 ++++---
.../api_fastapi/auth/managers/simple/ui/pnpm-lock.yaml | 12 ++++++------
airflow-core/src/airflow/ui/pnpm-lock.yaml | 8 ++++----
dev/README_RELEASE_PYTHON_CLIENT.md | 12 +++++++-----
4 files changed, 21 insertions(+), 18 deletions(-)
