7 Commits (0e5287d114497e2ffe2da788c28a84b09535ea8e)

Author	SHA1	Message	Date
Strycher	0e5287d114	chore(#516): cut 1.4.0+65 ... Bump pubspec to 1.4.0+65 and add the four release-gate docs for the follow-up to the 1.3.0 launch: button/buzzer settings for headless devices (#483), Send Again on channel messages (#513), caps byte 2 in Device Info (#480), and per-radio data-correctness fixes (#505/#506, #472, #425, #495, #497). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago
Strycher	c2d49d9691	chore(#465): cut 1.3.0+64 (first Play production release) ... Bump pubspec to 1.3.0+64 and add the four release-gate docs (CHANGELOG [1.3.0], GitHub release notes, Play what's-new, Discord post) covering everything since -62: the -63 store-consolidation fix plus the -64 feature batch (reactions, Observer config profiles, log/serial export, settings reorg, path diagnostics, reliability fixes). Includes an OKIMesh community thank-you for the first production launch. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago
Strycher	2994976897	chore(#367): cut 1.2.2+63 release (store consolidation notes + version) ... Bump pubspec to 1.2.2+63 and add the four release-gate docs (CHANGELOG section, GitHub release notes, Play what's-new, Discord post) for the #367/#370 desktop store-consolidation fix. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	2 months ago
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>	2 months ago
Strycher	b7606de536	chore(#359): cut 1.2.0+61 (version bump + release notes) ... Marketing version 1.2.0 (Ben's call: minor bump for a storage-engine migration + nav overhaul, not a patch). versionCode 61 (next after 60, current on Play). - pubspec 1.1.2-rc.3+60 -> 1.2.0+61 - CHANGELOG [1.2.0] section - release-notes/1.2.0.md (GitHub release body) - play/1.2.0.txt (498/500 chars) - discord/1.2.0.md Release-gate passes (all four texts present, play within limit). No em-dashes in the new copy. Headlines: drift/SQLite storage migration (auto-migrates existing data), new nav shell, cross-client GIF links. First release cut end-to-end through the #312 pipeline. Part of Play epic #160. Agent: SapphireCompass (session 8d755b5e)	2 months ago
Strycher	4f8b4c3736	feat(#342): author rc.3 release notes (GitHub / Play / Discord) ... The gate introduced in this PR correctly FAILED on its own PR in 8s: pubspec is rc.3, which had a CHANGELOG section but no notes files. That is the gate working exactly as intended, demonstrated live. Fix is the work we needed regardless: author rc.3's three per-audience notes. This also seeds dev so every future dev PR passes the gate (the current version now has all four files), and the rc.3 backfill branch will carry these to build the actual release. DRAFTS for owner review — the prose is mine, the judgement is Ben's. Play blurb is 403/500 chars. Part of epic #312, plan #321. Agent: SapphireCompass (session 8d755b5e)	2 months ago
Strycher	602776c601	feat(#342): full-platform release automation + four-file notes gate ... Today a tag builds and signs an APK/AAB but creates no release and attaches nothing. That is the same partial-release failure mode as rc.2/rc.3 (Play-only, no changelog). This closes it. release-signed.yml becomes a complete release pipeline off a v* tag: gate -> release-notes gate (backstop; fails in seconds) android -> signed APK + AAB, cert-verified (environment-gated) windows -> zipped Release build linux -> tarred bundle release -> create GitHub release, body = release notes, attach all four Security invariant preserved: only the android job references the release-signing Environment, so only it receives the keystore. The windows/linux/release jobs never see it. Still no pull_request trigger. The release job runs ONLY after every build passes, so a signing failure yields no release rather than an empty one. Published directly because the notes were reviewed in the cut PR. Four-file notes gate (.github/scripts/release-gate.sh), run on every PR (release-gate.yml) and as job one of the tag workflow: CHANGELOG.md section for the pubspec version release-notes/<v>.md non-empty -> GitHub release body play/<v>.txt non-empty, <=500 chars (Play limit) discord/<v>.md non-empty play and discord are human-pasted; CI validates, never sends. Any missing/oversize file fails the build, so a noteless release (rc.2/rc.3) is unmergeable. Gate script lives in .github/scripts/ because /scripts is in .git/info/exclude (would not commit). Verified locally: fail surfaces all four problems at once, pass is clean, 500 passes, 501 fails. Backfills the combined rc.2/rc.3 CHANGELOG entry the two versions shipped without. release-notes/, play/, discord/ seeded with README conventions. No ref input needed: the rc.3 backfill branch will carry these workflow files, so tagging that branch runs them at that commit. Part of epic #312, plan #321. Agent: SapphireCompass (session 8d755b5e)	2 months ago