feat(release): two channels, stable and nightly: no more release candidates #1768

Merged
HumanBean merged 1 commit from HumanBean/Longshot:feat/no-rc into main 2026-11-19 18:20:55 +00:00
Owner

We're dropping release candidates for both Longshot and the launcher: there will be only two channels, stable and nightly. A stable is tagged on a tested nightly's commit. This is Longshot's half; the launcher's is MagicBeanDev/LongshotLauncher#208.

What changes

  • Release tooling (scripts/release.py, tests/test_release.py, the same files as in the launcher's PR):

    • Only vX.Y.Z is a release, and next gives the next stable.
    • The "Earlier release candidates" notes are gone.
    • released-as finds a stable's nightly.

    cliff.toml's tag_pattern now matches stables only, so the old v3.0.0-rc.N tags don't split the notes.

  • CI.

    • Forgejo: release.yml, build-windows.yml and build-linux.yml drop -rc.N from their tag patterns and comments.
    • CircleCI (.circleci/shared.yml): the rc branches of the skip logic and the version patterns are gone. A stable still runs its full checks there, as before.
  • Website.

    • The worker offers stable and nightly, and the best channel is stable, else nightly.
    • Old /download/launcher/rc[/<os>] links still on rc release pages now go to stable rather than a 404.
    • The install page's channel picker and the launcher status line drop Release candidate.
    • The tests are updated, plus a new one for the rc redirect.
  • Docs.

    • RELEASING.md has one A stable section instead of the rc and stable-from-rc sections. It keeps Longshot's play-profile step, now before a minor's stable.
    • docs/releases.md (shared with the launcher), docs/versioning.md, docs/updates-and-saves.md, docs/development.md, README.md, CONTRIBUTING.md and the website README describe two channels.
  • Issue templates. The Channel dropdown loses Release candidate.

Left as it is

  • The game still shows RC7 in {build} for an old rc build (host/, the README's Discord status). Old builds exist, so that still describes something real.
  • The launcher screenshots in docs/images/guide still show an rc build: they were captured from launcher nightly-52. Recapturing them needs a released launcher and goes through the guide's manifest and source review, so it's a follow-up once a no-rc launcher nightly is out. scripts/screenshots/LauncherCapture.cs is unchanged until then, because it compiles against that pinned launcher.
  • MagicBeanDev/Tooling's release skill and the Discord relay (magicbean-infra) get their own changes.

Checks

  • Nothing under gpu/, host/, nx2/, assets/ or third_party/ changes, so nothing runs in the game.
  • py_compile passes on release.py and test_release.py.
  • I haven't run mise run test or the website's npm test: tests aren't run on this PC. They need a run elsewhere before this is ready.

πŸ€– Generated with Claude Code

We're dropping release candidates for both Longshot and the launcher: there will be only two channels, stable and nightly. A stable is tagged on a tested nightly's commit. This is Longshot's half; the launcher's is [MagicBeanDev/LongshotLauncher#208](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/208). ## What changes - **Release tooling** (`scripts/release.py`, `tests/test_release.py`, the same files as in the launcher's PR): - Only `vX.Y.Z` is a release, and `next` gives the next stable. - The "Earlier release candidates" notes are gone. - `released-as` finds a stable's nightly. `cliff.toml`'s `tag_pattern` now matches stables only, so the old `v3.0.0-rc.N` tags don't split the notes. - **CI.** - Forgejo: `release.yml`, `build-windows.yml` and `build-linux.yml` drop `-rc.N` from their tag patterns and comments. - CircleCI (`.circleci/shared.yml`): the rc branches of the skip logic and the version patterns are gone. A stable still runs its full checks there, as before. - **Website.** - The worker offers stable and nightly, and the best channel is stable, else nightly. - Old `/download/launcher/rc[/<os>]` links still on rc release pages now go to stable rather than a 404. - The install page's channel picker and the launcher status line drop *Release candidate*. - The tests are updated, plus a new one for the rc redirect. - **Docs.** - `RELEASING.md` has one *A stable* section instead of the rc and stable-from-rc sections. It keeps Longshot's play-profile step, now before a minor's stable. - `docs/releases.md` (shared with the launcher), `docs/versioning.md`, `docs/updates-and-saves.md`, `docs/development.md`, `README.md`, `CONTRIBUTING.md` and the website README describe two channels. - **Issue templates.** The Channel dropdown loses *Release candidate*. ## Left as it is - The game still shows `RC7` in `{build}` for an old rc build (`host/`, the README's Discord status). Old builds exist, so that still describes something real. - The launcher screenshots in `docs/images/guide` still show an `rc` build: they were captured from launcher `nightly-52`. Recapturing them needs a released launcher and goes through the guide's manifest and source review, so it's a follow-up once a no-rc launcher nightly is out. `scripts/screenshots/LauncherCapture.cs` is unchanged until then, because it compiles against that pinned launcher. - MagicBeanDev/Tooling's release skill and the Discord relay (magicbean-infra) get their own changes. ## Checks - Nothing under `gpu/`, `host/`, `nx2/`, `assets/` or `third_party/` changes, so nothing runs in the game. - `py_compile` passes on `release.py` and `test_release.py`. - I haven't run `mise run test` or the website's `npm test`: tests aren't run on this PC. They need a run elsewhere before this is ready. πŸ€– Generated with [Claude Code](https://claude.com/claude-code)
feat(release): two channels, stable and nightly: no more release candidates
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
Website / Website on Cloudflare (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 7s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 13s
CI / Workflow lint (actionlint) (pull_request) Successful in 13s
Third-party parts / As their notes say (pull_request) Successful in 16s
Website / Website on Cloudflare (pull_request_target) Has been skipped
PR description / Description follows the template (pull_request_target) Failing after 8s
bc823716c0
A stable is tagged on a tested nightly's commit. release.py, cliff.toml and
the workflows (Forgejo and CircleCI) take vX.Y.Z only; the website offers
stable and nightly, and its old /download/launcher/rc links go to stable;
RELEASING.md, the docs and the issue templates drop the rc channel.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Member

Possibly related, for context:

  • PR #638 feat(website): browse Nightly, RC and Stable release tabs β€” Open release-channel website work still presents an RC channel and overlaps website channel UI.
  • issue #394 Proposal: use the release structure we already have (nightly for testing, rc that means frozen) β€” Open proposal advocates keeping RCs, directly relevant to the channel policy this changes.
  • PR #168 feat(website): pick the launcher's channel on the install page β€” Merged install-page channel picker is the existing RC-aware UI this change updates.
  • PR #148 feat(release): big launcher download links in the README and on every release page, through magicbean.dev's permanent links β€” Merged release-link behavior routes users by channel, including RC links.
Possibly related, for context: - PR #638 feat(website): browse Nightly, RC and Stable release tabs β€” Open release-channel website work still presents an RC channel and overlaps website channel UI. - issue #394 Proposal: use the release structure we already have (nightly for testing, rc that means frozen) β€” Open proposal advocates keeping RCs, directly relevant to the channel policy this changes. - PR #168 feat(website): pick the launcher's channel on the install page β€” Merged install-page channel picker is the existing RC-aware UI this change updates. - PR #148 feat(release): big launcher download links in the README and on every release page, through magicbean.dev's permanent links β€” Merged release-link behavior routes users by channel, including RC links.
HumanBean changed title from WIP: feat(release): two channels, stable and nightly: no more release candidates to feat(release): two channels, stable and nightly: no more release candidates 2026-11-19 18:20:49 +00:00
HumanBean deleted branch feat/no-rc 2026-11-19 18:20:56 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MagicBeanDev/Longshot!1768
No description provided.