ci(release): attach per-version notes from PREVIOUS_HISTORY.md to releases

Per-version user-facing changelog moved out of the README table into
PREVIOUS_HISTORY.md (newest-first sections, Development Plan §11.1).
On tag push the workflow now harvests the matching section via
scripts/ci/release-notes.py and uses it as the release description,
uploading an Incido-<version>-changes.md beside the APKs; a missing
section falls back to the plain default description. CONTRIBUTING §5
documents the new release-notes maintenance step.
This commit is contained in:
Incido Developer committed 2026-09-17 15:43:20 +12:00
1 parent 576080c8b5
commit 7b6187f99a
5 files changed
+357 -3

No files matched your search

+4 -2
View File
@@ -63,8 +63,10 @@ adb install -r app/build/outputs/apk/debug/app-debug.apk
or your feature's manual verification steps.
### 5. Commit
We use [Conventional Commits](https://www.conventionalcommits.org/) so
the changelog can be generated automatically later:
We use [Conventional Commits](https://www.conventionalcommits.org/).
Per-version user-facing notes live in `PREVIOUS_HISTORY.md`
(Development Plan §11.1) — the release CI attaches the matching section
to each Gitea release automatically:
| Type | Use for |
|------|---------|