This is an automated email from the ASF dual-hosted git repository.
jasonliu pushed a change to branch backport-9da4a15-v3-1-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 789f1a6f290 [v3-1-test] grid merge node dict storage (#61656) (cherry
picked from commit 9da4a153b22854df7f9dd98cda093d33abd2488c)
add d53ec592db4 [v3-1-test] Amend simulation in release command (#61787)
(#61792)
add 963d1b3e520 Cherry-pick-missing-release-validator-tests (#61793)
add 79109fe9628 [v3-1-test] grid merge node dict storage (#61656) (cherry
picked from commit 9da4a153b22854df7f9dd98cda093d33abd2488c)
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 (789f1a6f290)
\
N -- N -- N refs/heads/backport-9da4a15-v3-1-test (79109fe9628)
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:
.../commands/release_candidate_command.py | 6 +-
.../src/airflow_breeze/commands/release_command.py | 51 +-
.../utils/airflow_release_validator.py | 597 ++++++++++++++++++++
.../src/airflow_breeze/utils/environment_check.py | 5 +-
.../src/airflow_breeze/utils/release_validator.py | 624 +++++++++++++++++++++
dev/breeze/tests/test_release_command.py | 81 ++-
6 files changed, 1323 insertions(+), 41 deletions(-)
create mode 100644
dev/breeze/src/airflow_breeze/utils/airflow_release_validator.py
copy shared/secrets_masker/tests/conftest.py =>
dev/breeze/src/airflow_breeze/utils/environment_check.py (85%)
create mode 100644 dev/breeze/src/airflow_breeze/utils/release_validator.py