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

pierrejeambrun pushed a change to branch v2-5-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


    omit e54970c333 Mention mapped operator in cluster policy doc (#28885)
    omit 3efa6d3019 Make secret rendering test more resilient to implementation 
details (#28673)
    omit 290f58bb9d Add automated version replacement in example dag indexes 
(#28090)
    omit 6f0cb81f17 Added --integration flag to "standard" set of flags for 
testing command (#28261)
    omit 3fd8e3422c Update Airflow version to 2.5.1
    omit a2422a516d Add Changelog for 2.5.1
     add 1a044ed77d Added --integration flag to "standard" set of flags for 
testing command (#28261)
     add 3c885de236 Add automated version replacement in example dag indexes 
(#28090)
     add 369c635130 Make secret rendering test more resilient to implementation 
details (#28673)
     add 1524392222 Mention mapped operator in cluster policy doc (#28885)
     add ee47f8b2d9 Update Airflow version to 2.5.1
     add 6aa136024b Add Changelog for 2.5.1

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   (e54970c333)
            \
             N -- N -- N   refs/heads/v2-5-test (6aa136024b)

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:

Reply via email to