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

Merged
HumanBean merged 1 commit from HumanBean/LongshotLauncher:feat/no-rc into main 2026-11-19 18:21:09 +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.

What changes

  • Channels. Versions.Channels is stable and nightly. vX.Y.Z-rc.N is no longer a version: an old rc release is on no channel and never offered, and the rc-follows-stable rules in ReleaseManifest, SelfUpdate, UpdatePolicy, Leftovers and OtherLauncher.ChannelNamed are gone.

  • Interface. The Release candidate row in the channel picker and the Track dropdown, the amber rc tag style, IsCandidate and DefaultIsCandidate, and the two strings in every translation.

  • Release tooling. scripts/release.py:

    • Takes vX.Y.Z only.
    • 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 old rc tags don't split a stable's notes. package.sh and the release.yml header no longer mention rc tags.

  • Docs. RELEASING.md has one A stable section (tag a tested nightly's commit, with a Windows tester first for Longshot) instead of the rc and stable-from-rc sections. docs/releases.md, README.md and CONTRIBUTING.md describe two channels.

Players with old rc builds

No migration code is needed, because the launcher already copes with what is left:

  • A saved "rc" channel is not a channel, so LauncherSettings.Load resets it and new builds go to stable.
  • A row on rc is moved to its version's track by BuildRegistry. An old v3.0.0-rc.N build lands on stable and is offered the stable's newest.

Old launchers on their rc channel keep updating to stables, since that channel already included them.

Before merging

Both products already have a stable (Longshot v3.0.0, the launcher v1.0.0), so nobody is left without one.

  • scripts/release.py and docs/releases.md are shared with Longshot. Its matching PR, with the website, the workflows and its issue templates, comes next.
  • #202, the redesign, will likely conflict on the channel tags and the channel picker.

Checks

  • dotnet build of the app, tools/screenshots and tests/launcher_core: no errors or warnings. py_compile passes on release.py and both Python test files.
  • I haven't run tests/test_launcher_core.py or tests/test_release.py: tests aren't run on this PC. They need a run elsewhere before this is ready.
  • I haven't launched the launcher.

🤖 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. ## What changes - **Channels.** `Versions.Channels` is stable and nightly. `vX.Y.Z-rc.N` is no longer a version: an old rc release is on no channel and never offered, and the rc-follows-stable rules in `ReleaseManifest`, `SelfUpdate`, `UpdatePolicy`, `Leftovers` and `OtherLauncher.ChannelNamed` are gone. - **Interface.** The *Release candidate* row in the channel picker and the Track dropdown, the amber `rc` tag style, `IsCandidate` and `DefaultIsCandidate`, and the two strings in every translation. - **Release tooling.** `scripts/release.py`: - Takes `vX.Y.Z` only. - `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 old rc tags don't split a stable's notes. `package.sh` and the `release.yml` header no longer mention rc tags. - **Docs.** `RELEASING.md` has one *A stable* section (tag a tested nightly's commit, with a Windows tester first for Longshot) instead of the rc and stable-from-rc sections. `docs/releases.md`, `README.md` and `CONTRIBUTING.md` describe two channels. ## Players with old rc builds No migration code is needed, because the launcher already copes with what is left: - A saved `"rc"` channel is not a channel, so `LauncherSettings.Load` resets it and new builds go to stable. - A row on `rc` is moved to its version's track by `BuildRegistry`. An old `v3.0.0-rc.N` build lands on stable and is offered the stable's newest. Old launchers on their rc channel keep updating to stables, since that channel already included them. ## Before merging Both products already have a stable (Longshot `v3.0.0`, the launcher `v1.0.0`), so nobody is left without one. - `scripts/release.py` and `docs/releases.md` are shared with Longshot. Its matching PR, with the website, the workflows and its issue templates, comes next. - [#202](https://git.magicbean.dev/MagicBeanDev/LongshotLauncher/pulls/202), the redesign, will likely conflict on the channel tags and the channel picker. ## Checks - `dotnet build` of the app, `tools/screenshots` and `tests/launcher_core`: no errors or warnings. `py_compile` passes on `release.py` and both Python test files. - I haven't run `tests/test_launcher_core.py` or `tests/test_release.py`: tests aren't run on this PC. They need a run elsewhere before this is ready. - I haven't launched the launcher. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(release): two channels, stable and nightly: no more release candidates
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 14s
f6c9cb92e2
A stable is tagged on a tested nightly's commit. The rc channel, its tags
(vX.Y.Z-rc.N), its notes and its row in the channel picker are gone. An old
rc tag is now no version: on no channel, never offered.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean force-pushed feat/no-rc from f6c9cb92e2
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 14s
to 0fe4c070f7
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 3s
2026-11-19 18:14:09 +00:00
Compare
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:21:01 +00:00
HumanBean deleted branch feat/no-rc 2026-11-19 18:21:10 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
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/LongshotLauncher!208
No description provided.