Repository navigation
Branch protection on release/v11 (and future release/vN) #270
Description
Sibling of milestone #13. RFC #267.
What
Apply branch protection to release/v11 (and document the policy so future release/vN get the same treatment when cut).
Acceptance criteria
- Required status checks:
ubuntu-latest(matchingmain's gate). - Linear history required (matches the
mainrebase/squash-only policy). - CODEOWNER review required on PRs targeting
release/v11. - Direct pushes blocked (except by maintainers using the established release-tagger account, if applicable).
- Tag protection:
v*tags can only be created by maintainers (limits who can fire a release). - Policy documented in
docs/agents/release-and-versioning.md(or wherever the branching docs live) so the same settings get applied whenrelease/v12is cut later.
Depends on
release/v11exists.
Activity
docs(agents): release-branch model + branch-protection policy for rel…
ChrisonSimtian commentedon May 29, 2026
Done. Both halves of #270 landed (PR #278 just merged):
release/v11— applied via API with a profile mirroringmain(requiredubuntu-latest, linear history, CODEOWNER reviews, force-push and deletion blocked, conversation resolution required, admins can bypass).docs/agents/release-and-versioning.md— new "Branch protection onrelease/vN" subsection so futurerelease/v12/etc. cuts mirror the same settings.Scope note
The tag-protection bullet from this issue's original acceptance criteria has been folded into #274 (comment) — release.yml refactor and tag protection are paired concerns and belong in the same PR.
What's unblocked next
ci: extend PR-validation triggers to release/v* branches (#291)
ci: extend PR-validation triggers to release/v* branches (#291) (#292)
docs: release-branch model — CONTRIBUTING + branching-and-release run…