feat(release): a nightly's notes list what is new since the nightly before #972

Merged
HumanBean merged 1 commit from HumanBean/Longshot:feat/nightly-notes-new-since into main 2026-11-15 23:46:03 +00:00
Owner

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.

  • release: previous_nightly() in scripts/release.py finds 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 over previous..HEAD, then over last version..previous.
  • tests: test_a_nightly_after_the_first_has_two_lists in tests/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:

  • None before merge: check the next nightly's release page.

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

  • 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 (not run on this PC; the checks run in Forgejo CI)
  • 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.

🤖 Generated with Claude Code

**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. - release: `previous_nightly()` in `scripts/release.py` finds 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 over `previous..HEAD`, then over `last version..previous`. - tests: `test_a_nightly_after_the_first_has_two_lists` in `tests/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:** - None before merge: check the next nightly's release page. ### 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 - [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`. - [ ] `python -I -B tests/run_all.py` passes (not run on this PC; the checks run in Forgejo CI) - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(release): a nightly's notes list what is new since the nightly before, then the earlier changes since the last version
Some checks failed
CI / Python source checks (ubuntu-24.04, part 1/2) (pull_request) Has been skipped
CI / Python source checks (ubuntu-24.04, part 2/2) (pull_request) Has been skipped
CI / SPIR-V fixtures (global narrow load/store, direct surface atomics, F2I immediate) (pull_request) Has been skipped
Third-party parts / The same as upstream (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 3s
Website / Website on Cloudflare (pull_request_target) Has been skipped
CI / Workflow lint (actionlint) (pull_request) Successful in 5s
Guide screenshots / Guide images and local UI source review (pull_request) Failing after 4s
Third-party parts / As their notes say (pull_request) Successful in 8s
PR description / Description follows the template (pull_request_target) Failing after 4s
8f3aa199d5
Co-Authored-By: Claude Sonnet 5.5 <[email protected]>
HumanBean changed title from WIP: feat(release): a nightly's notes list what is new since the nightly before to feat(release): a nightly's notes list what is new since the nightly before 2026-11-15 23:45:59 +00:00
HumanBean deleted branch feat/nightly-notes-new-since 2026-11-15 23:46:03 +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/Longshot!972
No description provided.