This is an automated email from the ASF dual-hosted git repository.
kaxilnaik pushed a change to branch v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit fa22c61ff11 Add Pydantic as dep for the Python Client (#50765)
omit 1bbc40ad011 Fix Airflow Python client generation for 3.0.0 (#50704)
omit 6873d55e8f9 [v3-0-test] Use Github API to fetch K8S schemas to fix
rate limiting (#50729) (#50731)
omit ceee1b940ad [v3-0-test] Add default ordering by map_index to patch TI
API (#50722) (#50725)
new cfde13a8644 [v3-0-test] Use Github API to fetch K8S schemas to fix
rate limiting (#50729) (#50731)
new 8cf5298c007 Fix Airflow Python client generation for 3.0.0 (#50704)
new f103f892e91 Add Pydantic as dep for the Python Client (#50765)
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 (fa22c61ff11)
\
N -- N -- N refs/heads/v3-0-test (f103f892e91)
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 3 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:
.../src/airflow/api_fastapi/core_api/routes/public/task_instances.py | 2 --
1 file changed, 2 deletions(-)
