This is an automated email from the ASF dual-hosted git repository.

vatsrahul1001 pushed a change to branch v3-3-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 32b1ffa982d [v3-3-test] Clarify when last_automated_data_interval is 
None in timetable docs (#68461) (#69227)
 discard 60081077727 [v3-3-test] Fix deadline callback data persistence 
(#69073) (#69259)
    omit 8e77f9e7d12 [v3-3-test] Fix retry policy overrides not persisted to 
task instance history (#69235) (#69241)
    omit a039c5f368f [v3-3-test] [AIP-94] Mark config CLI commands as migrated 
to airflowctl (#68958) (#69258)
    omit fc2feaaa287 [v3-3-test] Mark providers commands for airflowctl(#68525) 
(#69232)
    omit cb49e750491 [v3-3-test] Add new Committers to CODEOWNERS (#69215) 
(#69219)
    omit 4ec3ca401fa Update SQLAlchemy documentation links from 1.4 to 2.0 
(#69200) (#69203)
    omit 261fc1c9661 [v3-3-test] Fix drifting data intervals for monthly/yearly 
schedules with catchup disabled (#69143) (#69189)
     add fc7faf2bfd7 update release notes for 3.3.0rc1
     new 3ba9ddbcdba [v3-3-test] Fix drifting data intervals for monthly/yearly 
schedules with catchup disabled (#69143) (#69189)
     new 76893fb14ac Update SQLAlchemy documentation links from 1.4 to 2.0 
(#69200) (#69203)
     new 84590c18331 [v3-3-test] Add new Committers to CODEOWNERS (#69215) 
(#69219)
     new 7ebb7dc0c2b [v3-3-test] Mark providers commands for airflowctl(#68525) 
(#69232)
     new e9eda507cc8 [v3-3-test] [AIP-94] Mark config CLI commands as migrated 
to airflowctl (#68958) (#69258)
     new e3418895b40 [v3-3-test] Fix retry policy overrides not persisted to 
task instance history (#69235) (#69241)
     new 7fe134e787d [v3-3-test] Fix deadline callback data persistence 
(#69073) (#69259)
     new 767cee3c466 [v3-3-test] Clarify when last_automated_data_interval is 
None in timetable docs (#68461) (#69227)

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   (32b1ffa982d)
            \
             N -- N -- N   refs/heads/v3-3-test (767cee3c466)

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.

The 8 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 RELEASE_NOTES.rst          | 135 ++++++++++++++++++++++++---------------------
 docs/spelling_wordlist.txt |   1 +
 reproducible_build.yaml    |   4 +-
 3 files changed, 74 insertions(+), 66 deletions(-)

Reply via email to