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

ash pushed a change to branch single-base-url-for-ui
in repository https://gitbox.apache.org/repos/asf/airflow.git


 discard 4c79a8e26f7 Merge branch 'main' into single-base-url-for-ui
 discard f5f1c243d8c fixup! Use a single http tag to report the server's 
location to front end, not two
 discard dcc57c0be3b fixup! Use a single http tag to report the server's 
location to front end, not two
 discard 99f9dbda8e6 Use a single http tag to report the server's location to 
front end, not two
     add eb18f87f091 Stop trying to reconfigure the ORM in the OpenLineage 
workers (#47580)
     add 602ad81a0c6 Use a single http tag to report the server's location to 
front end, not two

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   (4c79a8e26f7)
            \
             N -- N -- N   refs/heads/single-base-url-for-ui (602ad81a0c6)

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:
 .../fab/src/airflow/providers/fab/auth_manager/fab_auth_manager.py  | 2 +-
 .../src/airflow/providers/openlineage/plugins/listener.py           | 6 ++++--
 2 files changed, 5 insertions(+), 3 deletions(-)

Reply via email to