This is an automated email from the ASF dual-hosted git repository.
ephraimanierobi pushed a change to branch v2-8-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit fcb2e589f7 Synchronize with latest ci.yml from main
omit aa91634652 Fix hard-coded branch name in CI workflow
omit f66f00f1d7 fixed wrong cherry-pick for asset compilation
omit e28a0dc972 Update RELEASE_NOTES.rst
add 0b296f5610 fixed wrong cherry-pick for asset compilation
add 01481e8897 Fix hard-coded branch name in CI workflow
add a0f4249989 Synchronize with latest ci.yml from main
add 9c5e8202f6 Load `consuming_dags` attr eagerly before dataset listener
(#36247)
add 38036ec861 Add version suffix if it is set during image builds (#36253)
add db2b75c233 Update RELEASE_NOTES.rst
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 (fcb2e589f7)
\
N -- N -- N refs/heads/v2-8-test (db2b75c233)
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:
RELEASE_NOTES.rst | 2 +-
airflow/datasets/manager.py | 7 ++++++-
dev/breeze/src/airflow_breeze/params/build_ci_params.py | 3 +--
dev/breeze/src/airflow_breeze/params/build_prod_params.py | 3 +--
.../src/airflow_breeze/params/common_build_params.py | 14 ++++++++++++++
5 files changed, 23 insertions(+), 6 deletions(-)
