Infer the RC from the target version during release. #59455
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This reduces the risk of error by ensuring a release is only performed when a corresponding RC exists and that the latest RC is selected automatically, rather than relying on manually supplied input.
ephraimbuddy
requested review from
amoghrajesh,
ashb,
bugraoz93,
gopidesupavan,
jason810496,
jedcunningham,
jscheffl,
kaxil and
potiuk
as code owners
boring-cyborg
bot
added
area:dev-tools
backport-to-v3-1-test
pierrejeambrun
approved these changes
Dec 15, 2025
Backport failed to create: v3-1-test. View the failure log Run details
You can attempt to backport this manually by running: cherry_picker a9f095e v3-1-testThis should apply the commit to the v3-1-test branch and leave the commit in conflict state marking After you have resolved the conflicts, you can continue the backport process by running: cherry_picker --continue |
ephraimbuddy
added a commit
that referenced
this pull request
Dec 15, 2025
This reduces the risk of error by ensuring a release is only performed when a corresponding RC exists and that the latest RC is selected automatically, rather than relying on manually supplied input. (cherry picked from commit a9f095e)
ephraimbuddy
added a commit
that referenced
this pull request
Dec 15, 2025
This reduces the risk of error by ensuring a release is only performed when a corresponding RC exists and that the latest RC is selected automatically, rather than relying on manually supplied input. (cherry picked from commit a9f095e)
TempestShaw
pushed a commit
to TempestShaw/airflow
that referenced
this pull request
Dec 24, 2025
This reduces the risk of error by ensuring a release is only performed when a corresponding RC exists and that the latest RC is selected automatically, rather than relying on manually supplied input.
ephraimbuddy
added a commit
that referenced
this pull request
Jan 6, 2026
This reduces the risk of error by ensuring a release is only performed when a corresponding RC exists and that the latest RC is selected automatically, rather than relying on manually supplied input. (cherry picked from commit a9f095e)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This reduces the risk of error by ensuring a release is only
performed when a corresponding RC exists and that the latest
RC is selected automatically, rather than relying on manually supplied input.