docs(agents): release-branch model + branch-protection policy for release/vN - #278
Merged
Merged
Conversation
…ease/vN (#270) Updates docs/agents/release-and-versioning.md to reflect the new branching model now that release/v11 has been cut (#269) and the auto-publish stopgap landed (#268). Branching section: - main is now the integration trunk (PRs target here), no longer auto-publishes - release/vN is the release channel per major (release/v11 exists; release/v12 will follow when v12 ships) - Hotfix flow noted as "cherry-pick from main" - Stale "No release/* branches" line removed New "Branch protection on release/vN" subsection captures the policy that gets applied to every release/vN at cut time: - Required ubuntu-latest status check - Linear history - CODEOWNER review required - Stale-approval dismissal - Direct pushes / force-pushes / deletions blocked - Conversation resolution required - Admins can bypass in emergencies Release pipeline section updated to acknowledge the workflow_dispatch stopgap and reference the pending tag-triggered shape under #274, and the NUGET_API_KEY move-to-environment-secret under #273. Closes #270 (the API-level branch protection on release/v11 was already applied; this PR is the documentation half of the acceptance criteria). Refs milestone #13, RFC #267. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
ChrisonSimtian
added
documentation
8 tasks
6 tasks
This was referenced Aug 7, 2026
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
1 participant
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.
Closes #270 (the doc half — the actual branch protection on
release/v11was applied via API; this PR captures the policy indocs/agents/release-and-versioning.mdso futurerelease/vNcuts mirror it).What changes
Branching section
mainis described as the integration trunk that no longer auto-publishes (per ci: stopgap — switch release workflow to workflow_dispatch only #268).release/vNas the per-major release channel.main.release/*branches" claim.New subsection: Branch protection on
release/vNCaptures the exact protection profile applied to
release/v11(mirroringmain's settings). Lists each rule so any futurerelease/vN(v12, v13...) gets the same treatment at cut time.Release pipeline section
Updated for accuracy — acknowledges the
workflow_dispatchstopgap (#268) and references the pending tag-triggered shape (#274) andNUGET_API_KEY-to-environment migration (#273). One outdated claim ("triggered on push to main") corrected.What this PR deliberately does NOT do
CONTRIBUTING.mdrewrite. That's part of the umbrella docs PR Document the release-branch model in CONTRIBUTING.md and /docs #276.docs/branching-and-release.md. Also Document the release-branch model in CONTRIBUTING.md and /docs #276.Verification
release/v11(gh api repos/.../branches/release/v11/protectionoutput diffs only on URL fields vs main's).🤖 Generated with Claude Code