This is an automated email from the ASF dual-hosted git repository.
utkarsharma pushed a change to branch v2-9-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 39a6307dc0 Update RELEASE_NOTES.rst
omit e37cd01e5c Update version to 2.9.3
omit 78a1ad1dfd Update trove classifiers to the latest version as build
dependency (#40542)
omit 7a2ed500f8 Update to latest pre-commit (#40529)
add 6ebf86e0d5 Update trove classifiers to the latest version as build
dependency (#40542)
add 698d819dce Update version to 2.9.3
add a65c0b29af Update RELEASE_NOTES.rst
add d9ad6f73cc Rename "try_number" increments that are unrelated to the
airflow concept (#39317)
add bbe9a01956 Fixup python client release guide (#39182)
add 670424b957 Upgrade to another version of trove-classifier (new CUDA
classifiers) (#40564)
add d53cdda996 Update to latest pre-commit (#40529)
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 (39a6307dc0)
\
N -- N -- N refs/heads/v2-9-test (d53cdda996)
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:
airflow/providers/amazon/aws/hooks/emr.py | 14 ++---
airflow/sensors/base.py | 14 ++---
dev/README_RELEASE_AIRFLOW.md | 2 +-
dev/README_RELEASE_PYTHON_CLIENT.md | 61 +++++++++++-----------
pyproject.toml | 2 +-
.../cncf/kubernetes/utils/test_pod_manager.py | 2 +-
6 files changed, 49 insertions(+), 46 deletions(-)
