This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch
dependabot/npm_and_yarn/airflow/www/v2-11-test/core-ui-package-updates-50ad2c7a2d
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard bda37c2c3a9 Bump the core-ui-package-updates group across 1 directory
with 87 updates
discard 942ca96ce90 chore(deps): bump the pip-dependency-updates group across
3 directories with 5 updates (#62808)
add 32aa5528164 [v2-11-test] fix missing logs in UI for tasks in
`UP_FOR_RETRY` and `UP_FOR_RESCHEDULE` states (#54547) (#62877)
add 05804912d35 chore(deps): bump the pip-dependency-updates group across
3 directories with 5 updates (#62808)
add f47a558d8f3 Bump the core-ui-package-updates group across 1 directory
with 87 updates
add 13803e42952 Revert "[v2-11-test] fix missing logs in UI for tasks in
`UP_FOR_RETRY` and `UP_FOR_RESCHEDULE` states (#54547) (#62877)"
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 (bda37c2c3a9)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airflow/www/v2-11-test/core-ui-package-updates-50ad2c7a2d
(13803e42952)
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: