feat(release): two channels, stable and nightly: no more release candidates #208
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/tooling
area/ui
area/updates
ci: approved
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
risk
high
risk
low
risk
medium
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
ci: approved
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!208
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:feat/no-rc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.Channelsis stable and nightly.vX.Y.Z-rc.Nis no longer a version: an old rc release is on no channel and never offered, and the rc-follows-stable rules inReleaseManifest,SelfUpdate,UpdatePolicy,LeftoversandOtherLauncher.ChannelNamedare gone.Interface. The Release candidate row in the channel picker and the Track dropdown, the amber
rctag style,IsCandidateandDefaultIsCandidate, and the two strings in every translation.Release tooling.
scripts/release.py:vX.Y.Zonly.nextgives the next stable.released-asfinds a stable's nightly.cliff.toml'stag_patternnow matches stables only, so old rc tags don't split a stable's notes.package.shand therelease.ymlheader no longer mention rc tags.Docs.
RELEASING.mdhas 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.mdandCONTRIBUTING.mddescribe two channels.Players with old rc builds
No migration code is needed, because the launcher already copes with what is left:
"rc"channel is not a channel, soLauncherSettings.Loadresets it and new builds go to stable.rcis moved to its version's track byBuildRegistry. An oldv3.0.0-rc.Nbuild 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 launcherv1.0.0), so nobody is left without one.scripts/release.pyanddocs/releases.mdare shared with Longshot. Its matching PR, with the website, the workflows and its issue templates, comes next.Checks
dotnet buildof the app,tools/screenshotsandtests/launcher_core: no errors or warnings.py_compilepasses onrelease.pyand both Python test files.tests/test_launcher_core.pyortests/test_release.py: tests aren't run on this PC. They need a run elsewhere before this is ready.🤖 Generated with Claude Code
f6c9cb92e20fe4c070f7WIP: feat(release): two channels, stable and nightly: no more release candidatesto feat(release): two channels, stable and nightly: no more release candidatesmadebyjordan referenced this pull request2026-11-19 19:42:36 +00:00