ci(release): no nightly when nothing new since the nightly before goes in its notes #133

Merged
HumanBean merged 1 commit from HumanBean/LongshotLauncher:ci/nightly-only-with-news into main 2026-11-16 06:12:22 +00:00
Owner

Type: ci · Risk: low · Tested on: none (the release workflow runs only on main) · Needs: none

Why

A push to main made of ci: or chore: commits alone makes a launcher nightly whose "new since" section is empty, because git-cliff leaves those commits out of the notes. Longshot's nightly-322-5bc54c6c is one, made of a single ci(release) commit. This repository has the same workflow.

What changed

This is the same change as in MagicBeanDev/Longshot: a nightly is not made when the commits since the nightly before would put nothing in its notes. The next one comes with what follows.

  • scripts/release.py: nightly_news() and release.py nightly-news (yes/no). It runs git-cliff with cliff.toml over <newest nightly on HEAD's history>..HEAD. The first nightly is always yes, and a nightly tag on HEAD itself doesn't count, so a nightly that is run again still builds.
  • .forgejo/workflows/release.yml, the version job: on a push, after the "main has moved on" check, it fetches the pinned git-cliff and asks nightly-news. If the answer is no, tag is left empty. If it gets no answer, it builds.
  • docs/releases.md: the rule.
  • tests/test_release.py: test_a_nightly_with_nothing_new_is_not_made.

Testing

Tested: the Python parses. I ran no checks on this PC; CI runs the tests.

Must be tested: after merge, this PR's own merge (ci:) should make no nightly, and the next listed commit should make one.

Risks

A commit that changes what ships but is titled chore: waits for the next listed commit. To turn it off, revert the commit.

🤖 Generated with Claude Code

**Type:** ci · **Risk:** low · **Tested on:** none (the release workflow runs only on main) · **Needs:** none ## Why A push to main made of `ci:` or `chore:` commits alone makes a launcher nightly whose "new since" section is empty, because git-cliff leaves those commits out of the notes. Longshot's [nightly-322-5bc54c6c](https://git.magicbean.dev/MagicBeanDev/Longshot/releases/tag/nightly-322-5bc54c6c) is one, made of a single `ci(release)` commit. This repository has the same workflow. ## What changed This is the same change as in MagicBeanDev/Longshot: a nightly is not made when the commits since the nightly before would put nothing in its notes. The next one comes with what follows. - `scripts/release.py`: `nightly_news()` and `release.py nightly-news` (yes/no). It runs git-cliff with `cliff.toml` over `<newest nightly on HEAD's history>..HEAD`. The first nightly is always yes, and a nightly tag on HEAD itself doesn't count, so a nightly that is run again still builds. - `.forgejo/workflows/release.yml`, the version job: on a push, after the "main has moved on" check, it fetches the pinned git-cliff and asks `nightly-news`. If the answer is no, `tag` is left empty. If it gets no answer, it builds. - `docs/releases.md`: the rule. - `tests/test_release.py`: `test_a_nightly_with_nothing_new_is_not_made`. ## Testing **Tested:** the Python parses. I ran no checks on this PC; CI runs the tests. **Must be tested:** after merge, this PR's own merge (`ci:`) should make no nightly, and the next listed commit should make one. ## Risks A commit that changes what ships but is titled `chore:` waits for the next listed commit. To turn it off, revert the commit. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ci(release): no nightly when nothing new since the nightly before goes in its notes
All checks were successful
CI / Compile and test (pull_request) Has been skipped
CI / Conventional Commit title (pull_request) Successful in 10s
9ef2152bab
nightly-322-5bc54c6c came of one ci(release) commit: git-cliff skips ci: and chore:, so its page had nothing new.
The version job now asks release.py nightly-news (git-cliff over the commits since the newest nightly on HEAD's
history) and makes no nightly when the answer is no; the next one comes with what follows. No answer: it builds.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
HumanBean changed title from WIP: ci(release): no nightly when nothing new since the nightly before goes in its notes to ci(release): no nightly when nothing new since the nightly before goes in its notes 2026-11-16 03:10:38 +00:00
HumanBean deleted branch ci/nightly-only-with-news 2026-11-16 06:12:23 +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/LongshotLauncher!133
No description provided.