feat(release): a nightly's notes list what is new since the nightly before #972
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/Longshot!972
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/Longshot:feat/nightly-notes-new-since"
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?
Type: feat · Risk: low · Tested on: not run locally (CI) · Needs: none
Why
A nightly's release page was one flat list of everything since the last version tag (v3.0.0-rc.4 for every nightly today), so a player opening a nightly could not tell what that nightly brought. A release candidate's page already splits "new since the rc before" from what the earlier ones brought; a nightly's now does the same.
What changed
A nightly's notes start with its own list, headed
## nightly-N-hash (date), new since nightly-M-hash, then## Earlier changes (since v3.0.0-rc.4)with the rest. The first nightly, and one whose predecessor is already the last version, keep one list.previous_nightly()inscripts/release.pyfinds the newest nightly tag on HEAD's history (the ones past the newest 5 are pruned, so it is the newest that is left);notes()runs git-cliff overprevious..HEAD, then overlast version..previous.test_a_nightly_after_the_first_has_two_listsintests/test_release.py.Measurements
Verdict: nothing to measure: release notes text, no game code.
Testing
Tested: not run locally (the PC this was written on runs no checks). The new test follows
test_an_rc_after_the_first_has_two_lists, with the same git-cliff stand-in.Not tested: a real git-cliff run over a real nightly; the first nightly built after this merges shows it.
Must be tested:
Flags and settings
None
Risks
What could break: a nightly's release notes (the release job, "The notes"); the build files are untouched.
Turning it off: revert the commit.
Compatibility: Nothing changes.
Checklist
Everyone
type(scope): description) of the status line's type.main.python -I -B tests/run_all.pypasses (not run on this PC; the checks run in Forgejo CI)third_party/untouched (a new folder with aPROVENANCE.mdinstead).When it applies
Assisted-by:/Co-Authored-By:trailers.🤖 Generated with Claude Code
WIP: feat(release): a nightly's notes list what is new since the nightly beforeto feat(release): a nightly's notes list what is new since the nightly before