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/3-1-core-ui-package-updates-72a1d69fb5
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 18b457a6653 chore(deps): bump the 3-1-core-ui-package-updates group
across 1 directory with 56 updates
add 5c629259b96 [v3-1-test] Add no-op _process_workloads to EdgeExecutor
to improve readability (#64236) (#64508)
add 0d05c6babe4 chore(deps): bump the 3-1-core-ui-package-updates group
across 1 directory with 56 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 (18b457a6653)
\
N -- N -- N
refs/heads/dependabot/npm_and_yarn/airflow-core/src/airflow/ui/v3-1-test/3-1-core-ui-package-updates-72a1d69fb5
(0d05c6babe4)
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/docs/core-concepts/executor/index.rst | 1 +
airflow-core/src/airflow/ui/package.json | 8 +-
airflow-core/src/airflow/ui/pnpm-lock.yaml | 579 +++++++++++----------
.../providers/edge3/executors/edge_executor.py | 9 +
4 files changed, 307 insertions(+), 290 deletions(-)
