feat(release): two channels, stable and nightly: no more release candidates #1768
No reviewers
Labels
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved
beanstalk: failed
beanstalk: needs approval
beanstalk: running
beanstalk: tested
ci: approved
good first issue
gpu/amd
gpu/igpu
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
needs measurements
platform/linux
platform/macos
platform/steam-deck
platform/windows
preview
priority
critical
priority
high
priority
low
regression
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!1768
Loadingβ¦
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot: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. 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):vX.Y.Zis a release, andnextgives the next stable.released-asfinds a stable's nightly.cliff.toml'stag_patternnow matches stables only, so the oldv3.0.0-rc.Ntags don't split the notes.CI.
release.yml,build-windows.ymlandbuild-linux.ymldrop-rc.Nfrom their tag patterns and comments..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.
/download/launcher/rc[/<os>]links still on rc release pages now go to stable rather than a 404.Docs.
RELEASING.mdhas 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.mdand the website README describe two channels.Issue templates. The Channel dropdown loses Release candidate.
Left as it is
RC7in{build}for an old rc build (host/, the README's Discord status). Old builds exist, so that still describes something real.docs/images/guidestill show anrcbuild: they were captured from launchernightly-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.csis unchanged until then, because it compiles against that pinned launcher.Checks
gpu/,host/,nx2/,assets/orthird_party/changes, so nothing runs in the game.py_compilepasses onrelease.pyandtest_release.py.mise run testor the website'snpm test: tests aren't run on this PC. They need a run elsewhere before this is ready.π€ Generated with Claude Code
Possibly related, for context:
WIP: feat(release): two channels, stable and nightly: no more release candidatesto feat(release): two channels, stable and nightly: no more release candidatesmooki referenced this pull request2026-11-19 19:52:22 +00:00