Repository navigation
Cut release/v11 branch from current main #269
Description
First concrete step of milestone #13. Driven by RFC #267.
What
Create a new branch release/v11 from the current main HEAD. From this point onward, release/v11 is the home of all v11.x releases; main continues to receive v11 work (cherry-picked back when needed) and is also where v12-prep starts.
Acceptance criteria
-
release/v11exists on origin, pointing at the chosen commit onmain. - No commits land directly on
release/v11yet — that comes with the cherry-pick / hotfix flow. - CHANGELOG entry under
[Unreleased] — 11.0→### Processnoting the cut and the new flow.
Notes
- The cut commit should be the latest stable
mainHEAD at execution time. No need to pick a special commit —mainis currently the source of truth. - The stopgap (ci: stopgap — switch release workflow to workflow_dispatch only #268) already disabled auto-releases on
main, so this cut doesn't race with an auto-publish. - Branch protection lands as a separate sibling issue.
Depends on
- Stopgap (ci: stopgap — switch release workflow to workflow_dispatch only #268) is merged ✓.
Blocks
- Branch protection on
release/v11. main'sversion.jsonbump to 12.0.- Refactor
release.ymlto tag-triggered.
Activity
ChrisonSimtian commentedon May 29, 2026
Done.
release/v11cut frommainHEAD.What landed
release/v114b19a8c1(=mainHEAD at cut time = the stopgap merge #268)gh api -X POST repos/.../git/refs ref=refs/heads/release/v11 sha=4b19a8c1...feat/fallout-core-88is untouched.Open PR survey
Only one open PR at cut time: #222 by
@dennisdoomen(target/v11, fixes GitVersion 6.x numeric field handling). Not retargeted — per Chris's standing preference, Dennis manages his own PRs. He'll retarget if/when he wants to.No Chris-authored PRs are currently open, so the "rebase ours onto
release/v11" part of this issue is a no-op.Verification
gh api repos/ChrisonSimtian/Fallout/branches/release/v11→ branch exists, sha4b19a8c1...,protected: falsemainandrelease/v11are identical at this instant (same SHA).What's still gated (next sub-issues)
release/v11(now unblocked)main'sversion.jsonto 12.0 (now unblocked)release.yml(still gated on env setup Create three GitHub Environments: nuget-org, github-packages, github-releases #272/Move NUGET_API_KEY from repo secret to nuget-org environment secret #273)CHANGELOG entry deferred to the umbrella docs PR (#276) so the v11 restructure gets one consolidated entry rather than nine fragmented ones.
docs(agents): release-branch model + branch-protection policy for rel…
docs: release-branch model — CONTRIBUTING + branching-and-release run…