This is an automated email from the ASF dual-hosted git repository.
utkarsharma pushed a change to branch Sync2-10-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
omit 49559fdee7 Update RELEASE_NOTES.rst
omit a122f3322b Update version to 2.10.1.
omit b08c8623bb Sync v2-10-stable with v2-10-test to release python client
v2.10.0 (#41610)
add 26d9857c4a Update release command for Airflow 2 (#41907)
add eefdfe33ad Upgrade UV to 0.4.1 (#41925) (#41926)
add 3b9935e780 Add backcompat check for executors that don't inherit
BaseExecutor (#41906) (#41927)
add beb5d5251a Sync v2-10-stable with v2-10-test to release python client
v2.10.0 (#41610)
add 9079231a81 Update version to 2.10.1.
add b254ed1cec 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 (49559fdee7)
\
N -- N -- N refs/heads/Sync2-10-test (b254ed1cec)
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:
.github/workflows/basic-tests.yml | 3 +-
Dockerfile | 2 +-
Dockerfile.ci | 4 +-
RELEASE_NOTES.rst | 1 +
airflow/jobs/scheduler_job_runner.py | 3 ++
airflow/reproducible_build.yaml | 4 +-
dev/README_RELEASE_AIRFLOW.md | 49 ++++++++++------------
.../output_release-management_start-rc-process.svg | 26 +++++++-----
.../output_release-management_start-rc-process.txt | 2 +-
.../commands/release_candidate_command.py | 10 +++--
.../commands/release_management_commands_config.py | 1 +
11 files changed, 55 insertions(+), 50 deletions(-)
