Re-enable branch protection on v3-3-stable#69131
Merged
Merged
Conversation
This reverts commit 74c5948.
ephraimbuddy
approved these changes
Jun 29, 2026
karenbraganz
pushed a commit
to karenbraganz/airflow
that referenced
this pull request
Jun 30, 2026
…che#69131) This reverts commit 74c5948.
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
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.
Now that 3.3.0 is in the RC phase, bring
v3-3-stableback under thev*-stableruleset by reverting the temporary exclusion added in #68993.#68993 excluded
v3-3-stablefrom branch protection so the branch could be created — under the rulesets migration (#66523) the linear-history rule rejects creating a newv*-stablebranch because its ancestry contains historical merge commits. Now that the branch exists, that exclusion is no longer needed: the RC sync is a fast-forward of an approved PR with a linear delta, the same operation 3.2.2 performed against a protectedv3-2-stable.Was generative AI tooling used to co-author this PR?
Generated-by: Claude Code (Opus 4.8) following the guidelines