docs(release-notes): unwrap PREVIOUS_HISTORY notes to single lines
dev / Build debug APK (push) Successful in 3m21s

release-notes.py copies each version section verbatim, so the hard-wrapping in the v0.4.0.0 and v0.3.8.1 sections (and the file preamble) shipped as premature returns in the Gitea release description and Incido-<version>-changes.md asset. Unwrap them to one line per note, matching every section from v0.3.8.0 down. Also normalise the redundant '- **Title.** — desc' bullet heads to the house '- **Title.** desc' style across the file. Record the rule (write each note as one complete line; the release UI reflows it) in Development Plan 11.1 and CONTRIBUTING 5 so it does not recur.
This commit is contained in:
Incido Developer committed 2026-09-18 17:58:21 +12:00
1 parent ffa821bf28
commit 3d234f307e
3 files changed
+32 -54

No files matched your search

+5 -1
View File
@@ -435,7 +435,11 @@ A small Gradle task called `copyReleaseApks` (registered in
line. **`PREVIOUS_HISTORY.md`** — append a new
`## v<NEW_VERSION> — <DATE>` section at the top: friendly user-facing
bullets, newest first (this file replaced the old README Changelog
table). On tag push the release workflow runs
table). **Write each note (paragraph or bullet) as one complete line —
do not hard-wrap it:** the CI copies the section verbatim into the release
description and the `Incido-<version>-changes.md` asset, so a manual line
break ships as a premature return; the release UI reflows the text for you.
On tag push the release workflow runs
`scripts/ci/release-notes.py` and attaches that section to the Gitea
release as its description **and** as an `Incido-<version>-changes.md`
asset beside the APKs — so keep one section per released version and