This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/npm_and_yarn/airflow/www/v2-10-test/core-ui-package-updates-10f4bb6835
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard baf3626f446 Bump the core-ui-package-updates group across 1 directory
with 85 updates
add abf9d22506e [v2-10-test] Fix: Make Breeze `uv.lock` up to date (#48404)
add e2974872f5e Store rendered_map_index from TaskInstancePydantic into
TaskInstance (#48571)
add f1e9e267d0a Bump the core-ui-package-updates group across 1 directory
with 85 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 (baf3626f446)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airflow/www/v2-10-test/core-ui-package-updates-10f4bb6835
(f1e9e267d0a)
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/models/taskinstance.py | 1 +
airflow/www/package.json | 10 +-
airflow/www/yarn.lock | 96 ++++-----
dev/breeze/README.md | 2 +-
dev/breeze/uv.lock | 429 ++++++++++++++++++++++++++++++++++----
tests/models/test_taskinstance.py | 5 +-
6 files changed, 442 insertions(+), 101 deletions(-)
