This is an automated email from the ASF dual-hosted git repository.
vatsrahul1001 pushed a change to branch backport-7468d31-v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 2586aef8197 [v3-4-test] Show UI doc screenshots in synced dark/light
tabs (#75957)
add f161c4d6def [v3-4-test] Fix hourly cron schedules running an hour off
across a DST change (#75847) (#75953)
add 876410cc751 [v3-4-test] Remove unused milestone selection helpers
(#75848) (#75925)
add 72b1311fc84 [v3-4-test] Remove unused decorator default comparison
helper (#75849) (#75926)
add dfa73fddf07 [v3-4-test] Stop a stale callback stat from forcing
constant Dag file reparsing (#73433) (#75939)
add dd1ed6e3bc8 [v3-4-test] Show UI doc screenshots in synced dark/light
tabs (#75957)
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 (2586aef8197)
\
N -- N -- N refs/heads/backport-7468d31-v3-4-test (dd1ed6e3bc8)
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/dag_processing/manager.py | 19 +-
airflow-core/src/airflow/timetables/_cron.py | 69 ++++-
.../tests/unit/dag_processing/test_manager.py | 112 ++++++++-
.../tests/unit/timetables/test_cron_mixin.py | 279 ++++++++++++++++++++-
.../src/airflow_breeze/commands/ci_commands.py | 39 ---
dev/breeze/tests/test_set_milestone.py | 48 ----
scripts/ci/prek/check_init_decorator_arguments.py | 15 --
7 files changed, 466 insertions(+), 115 deletions(-)
