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

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


    omit a55999854f Upgrade to FAB 4.5.0 (#39851)
    omit edc3a9d87a Fix mocking in kerberos integration test (#40042)
    omit 0065c37196 Fix `update-common-sql-api-stubs` pre-commit check (#38915)
    omit 1d5730d7e8 Clean up Breeze output for Docker context (#38857)
    omit ec30727b14 Add "use self-hosted runners" to CI setup (#38779)
    omit 7c2aef58b7 Replace to broad exceptions into the dev (#38489)
    omit e67fb2849e Fix inconsistency of cache-directive vs. docker-cache 
(#38580)
    omit 22165b18ad Add hatch_build.py to k8s test venv cache calculation 
(#39473)
    omit 0704532d00 Increase volume size for ARM instance (#39472)
    omit ec3876711c add lost space to breeze help (#39458)
    omit 9e222e8aea Update uv and build dependencies. (#39808)
    omit 720eef88f8 Update RELEASE_NOTES.rst
    omit c6833fdc85 Update version to 2.9.2
     add 355d546911 Update uv and build dependencies. (#39808)
     add 3d260e63c9 add lost space to breeze help (#39458)
     add 7a6da92e5d Increase volume size for ARM instance (#39472)
     add 0ef6d4f561 Add hatch_build.py to k8s test venv cache calculation 
(#39473)
     add f8fa6c4be5 Fix inconsistency of cache-directive vs. docker-cache 
(#38580)
     add 61b5b7d231 Replace to broad exceptions into the dev (#38489)
     add 21625dc981 Add "use self-hosted runners" to CI setup (#38779)
     add d281480cb3 Clean up Breeze output for Docker context (#38857)
     add 4fd65ab0fc Fix `update-common-sql-api-stubs` pre-commit check (#38915)
     add a761b81f0b Fix mocking in kerberos integration test (#40042)
     add da5260f2f5 Upgrade to FAB 4.5.0 (#39851)
     add 2208af9d0c Update version to 2.9.2
     add 600da55c68 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   (a55999854f)
            \
             N -- N -- N   refs/heads/v2-9-test (600da55c68)

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