Repository navigation
Re-enable branch protection on v3-4-stable - #75477
Merged
Merged
Conversation
kaxil
approved these changes
Oct 23, 2026
1 task done
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
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.
Summary
Restores branch protection for
v3-4-stablenow that the branch has been created, reverting #75473.Protection was temporarily lifted only so the
v3-4-stablebranch could be created (thev*-stableruleset blocks creation of matching branches). With the branch in place, it should be protected again for the remainder of the 3.4.0 release: all further changes (rc sync PRs, GA) land through reviewed, linear PRs, and the branch is safe from direct/force pushes during the RC vote.Mirrors #69131 (the equivalent re-enable for
v3-3-stableat 3.3.0).🤖 Generated with Claude Code