Update backport label to v3-2-test and improve release docs#64338
Merged
potiuk merged 1 commit intoapache:mainfrom Mar 29, 2026
Merged
Update backport label to v3-2-test and improve release docs#64338potiuk merged 1 commit intoapache:mainfrom
potiuk merged 1 commit intoapache:mainfrom
Conversation
potiuk
requested review from
bugraoz93,
jedcunningham,
jscheffl,
shahar1 and
vincbeck
as code owners
eladkal
approved these changes
Mar 28, 2026
vatsrahul1001
approved these changes
Mar 28, 2026
bugraoz93
approved these changes
Mar 28, 2026
potiuk
force-pushed
the
update-backport-label-v3-2
branch
from
28ac9c5 to
1c69c07
Compare
potiuk
requested review from
amoghrajesh,
ashb,
choo121600,
gopidesupavan and
jason810496
as code owners
potiuk
force-pushed
the
update-backport-label-v3-2
branch
from
1c69c07 to
99eb68f
Compare
jscheffl
approved these changes
Mar 28, 2026
- Rename boring-cyborg backport label from v3-1-test to v3-2-test - Remove files from backport that only make sense on main branch - Remove outdated CI cherry-pick instructions from release docs - Add steps for creating backport label and updating boring-cyborg
potiuk
force-pushed
the
update-backport-label-v3-2
branch
from
99eb68f to
fe7bccc
Compare
Backport failed to create: v3-1-test. View the failure log Run detailsNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
You can attempt to backport this manually by running: cherry_picker 4ce1412 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 --continueIf you don't have cherry-picker installed, see the installation guide. |
Suraj-kumar00
pushed a commit
to Suraj-kumar00/airflow
that referenced
this pull request
Apr 7, 2026
…4338) - Rename boring-cyborg backport label from v3-1-test to v3-2-test - Remove files from backport that only make sense on main branch - Remove outdated CI cherry-pick instructions from release docs - Add steps for creating backport label and updating boring-cyborg
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
v3-1-testtov3-2-testWas generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Claude Opus 4.6) following the guidelines