Hide empty testing batches in changelog

This commit is contained in:
2026-09-04 20:32:35 -07:00
parent 4eb9e6c96a
commit 79f3d40fcd
4 changed files with 11 additions and 3 deletions
+1
View File
@@ -44,6 +44,7 @@ The app shows its version number and a player-facing changelog in the ☰ menu
- Ordinary commits do **not** bump `VERSION` or the Nix package versions.
- Accumulate player-visible changes in one entry at the **top** of `CHANGELOG` with `version: null` and `changes: [...]`. The About dialog labels it **In testing**. Append to or consolidate this batch across commits; do not create a separate entry per commit or assign a release date yet.
- Omit the In testing entry when there are no unreleased player-facing changes; empty batches are hidden. Do not add placeholder entries just to describe changelog maintenance.
- The changelog is for players: skip refactors, tests, tooling, and other internal-only changes. Internal-only commits need no changelog entry.
- Release labeling is a separate process, performed only when explicitly requested. At release time:
1. Consolidate the In testing batch into meaningful player-facing groups using `groups: [{ title, changes: [...] }]`, replacing its flat `changes` list. Remove duplicates and describe the final behavior.