History

Strycher 60e865b900 chore(#365 ): cut 1.2.1+62 (desktop DB-path P0 patch notes + version bump) Bump pubspec 1.2.0+61 -> 1.2.1+62 and add the four-file notes gate for the 1.2.1 release: CHANGELOG section, release-notes/1.2.1.md, play/1.2.1.txt (274/500), discord/1.2.1.md. Ships the #363/#364 desktop drift DB-path fix. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		9 hours ago
..
1.1.2-rc.3.md	feat(#342 ): author rc.3 release notes (GitHub / Play / Discord)	24 hours ago
1.2.0.md	docs(#359 ): put the offband.app URLs back in	18 hours ago
1.2.1.md	chore(#365 ): cut 1.2.1+62 (desktop DB-path P0 patch notes + version bump)	9 hours ago
README.md	feat(#342 ): full-platform release automation + four-file notes gate	24 hours ago

README.md

GitHub release notes

One file per release: release-notes/<version>.md, where <version> is the marketing version from pubspec.yaml (the part before +), e.g. release-notes/1.1.2-rc.4.md.

CI sets the GitHub release body from this file verbatim. It is published directly — the notes are reviewed in the release-cut PR, so there is no draft step. What is in this file at tag time is what the world sees.

Style

Narrative prose, not a bulleted changelog. Written for someone deciding whether to install or update: what's new, what got fixed, anything they should know. Full Markdown is fine.

This is distinct from:

CHANGELOG.md — cumulative, terse, issue-referenced, for developers.
play/<version>.txt — plain, ≤500 chars, for the store.
discord/<version>.md — casual community announcement.

Same underlying changes, four different voices. The release gate (scripts/release-gate.sh) fails the build if this file is missing or empty for the version being tagged.