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

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


 discard 825a1f2  Revert "Fix handling some None parameters in kubernetes 23 
libs. (#21905)"
 discard ea476f9  Revert "Update Kubernetes library version (#18797)"
 discard e0a6b67  Revert "Remove RefreshConfiguration workaround for K8s token 
refreshing (#20759)"
    omit e0754a4  Fix rat-exclides and issue template licence (#22550)
    omit 52499a7  Add 2.2.5 to CHANGELOG.txt and UPDATING.md
     new 6bbcb33  Fix rat-exclides and issue template licence (#22550)
     new 9597880  Revert "Remove RefreshConfiguration workaround for K8s token 
refreshing (#20759)"
     new cbfae04  Revert "Update Kubernetes library version (#18797)"
     new d11c2e9  Revert "Fix handling some None parameters in kubernetes 23 
libs. (#21905)"
     new 3da4cb7  Add 2.2.5 to CHANGELOG.txt and UPDATING.md

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   (825a1f2)
            \
             N -- N -- N   refs/heads/v2-2-test (3da4cb7)

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 5 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:
 CHANGELOG.txt | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

Reply via email to