MagicBeanDev/Longshot
MagicBeanDev/Longshot
Watch
75
97
Fork
You've already forked Longshot
 101
Code Issues 237 Pull requests 245 Projects Releases 9 Packages Wiki Activity Actions 760

feat(release): an rc's notes list what's new since the rc before, then the earlier release candidates #745

Merged
HumanBean merged 1 commit from HumanBean/Longshot:feat/rc-notes into main 2026-11-15 18:14:01 +00:00
Conversation 0 Commits 1 Files changed 4 +92 -14
HumanBean commented 2026-11-15 09:16:07 +00:00
Owner

Type: feat · Risk: low · Tested on: Linux (the notes of v3.0.0-rc.4 and the launcher's v1.0.0-rc.6) · Needs: none

Why

A release candidate's page lists only what changed since the rc before, so a player coming from the last stable, or new to Longshot, can't see everything the version brings. With two lists, players on the previous rc see what's new for them, and the second list shows the rest.

What changed

release.py notes for an rc after the first (e.g. rc.3) writes two lists: ## v3.0.0-rc.3 (<date>), new since rc.2 (git-cliff over rc.2..rc.3, as before), then ## Earlier release candidates: rc.1, rc.2 (since <stable>), what those brought since the last stable (here the fork) in one list. A first rc, a stable and nightlies keep one list.

  • scripts/release.py: earlier_rcs (the rcs since the last stable before this one), git_cliff, and notes' second list: git-cliff over <stable or the fork>..<last earlier rc> with --ignore-tags for rc tags, so it doesn't split per rc.
  • tests/test_release.py: the two lists, and the launcher's no-stable case (no range, --skip-commit for the newer commits).
  • docs/releases.md, Release notes: the two lists.
  • .claude/skills/release/SKILL.md: for an rc after the first, the What's new summarizes the first list.

The same change goes to the launcher (release.py and docs/releases.md are shared): MagicBeanDev/LongshotLauncher#92.

Measurements

Verdict: nothing to measure: release notes text.

Flags and settings

None

Testing

Tested: python -I scripts/release.py notes v3.0.0-rc.4 with the pinned git-cliff gives ## v3.0.0-rc.4 (2026-11-15), new since rc.3, then ## Earlier release candidates: rc.1, rc.2, rc.3. python -I tests/test_release.py: OK. python -I -B tests/run_all.py: 509 passed, 14 failed, 70 skipped; the same 14 as on main (test_make_game_cache, test_lift_cleanup_error, test_bake_portability, test_crash_dialog, test_cpm_discovery, test_env_on, test_appimage_player_build, test_linux_preflight, test_options_budget_once, test_pipeline_tour, test_mods_size_table, test_readback_late, test_vk_pgo, test_walk_key), none touching release.py. In the launcher, rc.6's notes give the same shape over 5 earlier rcs.

Not tested: a real release with it (the next rc will be the first).

Must be tested: None

Risks

What could break: an rc's release notes. A git-cliff failure stops the release workflow's The notes step before anything is published, as before.

Turning it off: revert the commit

Compatibility: Nothing changes

Checklist

Everyone

  • One topic.
  • The title is a Conventional Commit (type(scope): description) of the status line's type.
  • Why gives the reason plainly and links the issues that fit (the tracker searched).
  • Measurements has a verdict, or one line saying why there is nothing to measure.
  • Testing names what was tested, what wasn't, and what must still be tested, where and how.
  • Rebased on current main.
  • python -I -B tests/run_all.py passes (any failure that also fails on main is named).
  • No game files, dumps, build output or generated files.
  • third_party/ untouched (a new folder with a PROVENANCE.md instead).
  • The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

When it applies

  • AI assistance recorded with Assisted-by: / Co-Authored-By: trailers.
  • A check under tests/ that reads changed source updated in this PR, not weakened.
  • Docs updated.

🤖 Generated with Claude Code

**Type:** feat · **Risk:** low · **Tested on:** Linux (the notes of v3.0.0-rc.4 and the launcher's v1.0.0-rc.6) · **Needs:** none ## Why A release candidate's page lists only what changed since the rc before, so a player coming from the last stable, or new to Longshot, can't see everything the version brings. With two lists, players on the previous rc see what's new for them, and the second list shows the rest. ## What changed `release.py notes` for an rc after the first (e.g. rc.3) writes two lists: `## v3.0.0-rc.3 (<date>), new since rc.2` (git-cliff over rc.2..rc.3, as before), then `## Earlier release candidates: rc.1, rc.2 (since <stable>)`, what those brought since the last stable (here the fork) in one list. A first rc, a stable and nightlies keep one list. - `scripts/release.py`: `earlier_rcs` (the rcs since the last stable before this one), `git_cliff`, and `notes`' second list: git-cliff over `<stable or the fork>..<last earlier rc>` with `--ignore-tags` for rc tags, so it doesn't split per rc. - `tests/test_release.py`: the two lists, and the launcher's no-stable case (no range, `--skip-commit` for the newer commits). - `docs/releases.md`, *Release notes*: the two lists. - `.claude/skills/release/SKILL.md`: for an rc after the first, the What's new summarizes the first list. The same change goes to the launcher (`release.py` and docs/releases.md are shared): MagicBeanDev/LongshotLauncher#92. ## Measurements **Verdict:** nothing to measure: release notes text. ### Flags and settings None ## Testing **Tested:** `python -I scripts/release.py notes v3.0.0-rc.4` with the pinned git-cliff gives `## v3.0.0-rc.4 (2026-11-15), new since rc.3`, then `## Earlier release candidates: rc.1, rc.2, rc.3`. `python -I tests/test_release.py`: OK. `python -I -B tests/run_all.py`: 509 passed, 14 failed, 70 skipped; the same 14 as on `main` (test_make_game_cache, test_lift_cleanup_error, test_bake_portability, test_crash_dialog, test_cpm_discovery, test_env_on, test_appimage_player_build, test_linux_preflight, test_options_budget_once, test_pipeline_tour, test_mods_size_table, test_readback_late, test_vk_pgo, test_walk_key), none touching release.py. In the launcher, rc.6's notes give the same shape over 5 earlier rcs. **Not tested:** a real release with it (the next rc will be the first). **Must be tested:** None ## Risks **What could break:** an rc's release notes. A git-cliff failure stops the release workflow's *The notes* step before anything is published, as before. **Turning it off:** revert the commit **Compatibility:** Nothing changes ## Checklist ### Everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`) of the status line's type. - [x] Why gives the reason plainly and links the issues that fit (the tracker searched). - [x] Measurements has a verdict, or one line saying why there is nothing to measure. - [x] Testing names what was tested, what wasn't, and what must still be tested, where and how. - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` passes (any failure that also fails on `main` is named). - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled. ### When it applies - [x] AI assistance recorded with `Assisted-by:` / `Co-Authored-By:` trailers. - [x] A check under `tests/` that reads changed source updated in this PR, not weakened. - [x] Docs updated. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(release): an rc's notes list what's new since the rc before, then the earlier release candidates
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
Details
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
Details
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Details
Third-party parts / The same as upstream (pull_request) Has been skipped
Details
CI / Conventional Commit title (pull_request) Successful in 13s
Details
CI / Workflow lint (actionlint) (pull_request) Successful in 20s
Details
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 18s
Details
Third-party parts / As their notes say (pull_request) Successful in 27s
Details
PR description / Description follows the template (pull_request_target) Successful in 15s
Details
Website / Website on Cloudflare (pull_request_target) Has been skipped
Details
3e07cae0be 
Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean deleted branch feat/rc-notes 2026-11-15 18:14:02 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels   
area/accessibility
Barriers for people with disabilities

  
area/audio
Sound and music

  
area/input
Controllers, keyboard, mouse

  
area/install
Installing, updating, building from your game

  
area/menu
In-game menu and settings

  
area/renderer
Vulkan renderer, shaders, effects

  
area/saves
Save files

  
area/tooling
Developer tools: scripts, CI, build and release tooling

  
area/upscaling
DLSS, FSR, frame generation

  
beanstalk: approved @ 1697603
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 2c5a62e
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 4fd82b7
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 64d6d09
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 6f91fae
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 70a78f9
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 8015c9a
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 8d361dc
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ 9d8356e
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ abf2227
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ d82f202
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ e5f1e40
Set by Beanstalk for show; the farm's database is what counts

  
beanstalk: approved @ ee8ab5f
Set by Beanstalk for show; the farm's database is what counts

  
ci: approved
A maintainer approved CircleCI for this fork PR (sticky; removed after 14 quiet days)

  
good first issue
A good start for a new contributor

  
gpu/amd
AMD GPUs

  
gpu/igpu
Integrated GPUs

  
gpu/intel
Intel GPUs

  
gpu/nvidia
NVIDIA GPUs

  
help wanted
Extra hands or knowledge wanted

  
kind
bug
 Something doesn't work as it should

  
kind
chore
 Build, CI, dependencies, tidying

  
kind
docs
 Documentation

  
kind
feature
 A new feature or an improvement

  
kind
performance
 Frame rate, frame time, loading, memory

  
kind
question
 A question rather than a change

  
needs measurements
Waiting for before/after measurements

  
platform/linux
Affects Linux (a change for every system carries both Windows and Linux)

  
platform/macos
macOS (Apple silicon or Intel Macs)

  
platform/steam-deck
Steam Deck

  
platform/windows
Affects Windows (a change for every system carries both Windows and Linux)

  
preview
Maintainers: deploy a preview of this PR's website (read its changes first). Removed after the run.

  
priority
critical
 Crashes, data loss, or blocks most players

  
priority
high
 Important: next in line

  
priority
low
 Nice to have

  
regression
Worked in an earlier build, broken in a newer one: highest priority, above other bugs

  
risk
high
 Broad or core change: the renderer, defaults on many systems, saves, installs, security

  
risk
low
 Small, contained change: little can break

  
risk
medium
 Changes behaviour in one area, or a default on some systems

  
status
blocked
 Waits on something else first

  
status
confirmed
 Reproduced or agreed on

  
status
duplicate
 Already reported or proposed

  
status
invalid
 Not a problem in this project

  
status
needs-info
 Waiting for more information from the reporter

  
status
wontfix
 Will not be worked on

  
testing wanted
Wanted: a test on other hardware (posts a test request in #test-requests)

  
ci: approved
No labels
area/accessibility
area/audio
area/input
area/install
area/menu
area/renderer
area/saves
area/tooling
area/upscaling
beanstalk: approved @ 1697603
beanstalk: approved @ 2c5a62e
beanstalk: approved @ 4fd82b7
beanstalk: approved @ 64d6d09
beanstalk: approved @ 6f91fae
beanstalk: approved @ 70a78f9
beanstalk: approved @ 8015c9a
beanstalk: approved @ 8d361dc
beanstalk: approved @ 9d8356e
beanstalk: approved @ abf2227
beanstalk: approved @ d82f202
beanstalk: approved @ e5f1e40
beanstalk: approved @ ee8ab5f
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
testing wanted
ci: approved
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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/Longshot!745
No description provided.