[cd] Replace versioned release branches with fixed `releases/lts/*` refs (#99807)
Release branches no longer carry the version number. Two long-lived,
manually-created branches replace them: `releases/lts/active` (current
major's release line) and `releases/lts/maintenance` (previous major's).
From then on, triggering a stable release moves the refs automatically,
via the release GitHub App (next.js bot) credentials already used for
the signed release commit:
- **patch**: no ref moves — the release commit already advances the
branch it was cut on
- **minor**: routed by the released version's major against the latest
major (the one `releases/lts/active` currently points at) — equal moves
`releases/lts/active` to the new tag, latest − 1 moves
`releases/lts/maintenance` to the new tag, anything else moves nothing
- **major**: `releases/lts/maintenance` takes `releases/lts/active`'s
previous position, then `releases/lts/active` moves to the new tag
Supporting changes:
- `scripts/release-branches.json` lists the fixed branch set (`canary` +
both LTS branches) so `version-bump.js` allows bumps on them
- `build_and_test.yml` / `build_and_deploy.yml` run on pushes to the LTS
branches, and the staging deploy-target condition covers them (parity
with the per-branch rewrite the removed script used to produce)
- `backport-pr` skill, `AGENTS.md`, `release-channels-publishing.md`,
and a stale `version-bump.js` comment updated for the new branch model
Co-authored-by:
Claude Code <noreply@anthropic.com>
Showing
Please
register
or
sign in
to comment