This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch
dependabot/uv/dev/breeze/uv-dependency-updates-bde0296d34
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 45fec4a59d2 Bump the uv-dependency-updates group across 1 directory
with 5 updates
add 7daad99dd26 Bump react-hotkeys-hook in /airflow-core/src/airflow/ui
(#69723)
add 650fc200761 Bump @stylistic/eslint-plugin in
/airflow-core/src/airflow/ui (#69720)
add 583369271f5 Fix generate-providers-metadata hang by using spawn pools
(#69763)
add 6bef6a5d2d4 Fix Azure Data Factory test broken by
azure-mgmt-datafactory update (#69785)
add 13bc6ead887 Bump the uv-dependency-updates group across 1 directory
with 5 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 (45fec4a59d2)
\
N -- N -- N
refs/heads/dependabot/uv/dev/breeze/uv-dependency-updates-bde0296d34
(13bc6ead887)
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:
airflow-core/src/airflow/ui/package.json | 4 +-
airflow-core/src/airflow/ui/pnpm-lock.yaml | 115 +++++++++------------
.../commands/release_management_commands.py | 9 +-
.../airflow_breeze/utils/provider_dependencies.py | 9 +-
dev/breeze/uv.lock | 12 +--
.../microsoft/azure/hooks/test_data_factory.py | 3 +-
6 files changed, 72 insertions(+), 80 deletions(-)
