From cf696d3da542d6e96401e547557f4ad61803045c Mon Sep 17 00:00:00 2001 From: Paul Schneider Date: Sun, 16 Aug 2026 17:05:03 +0100 Subject: [PATCH] release: declare '- stable' substring inside the [1.0.6] body The validate-release job in .github/workflows/docker-publish-android.yml uses an awk script to extract the section body, with a 'next' that skips the '## [TAG]' title line. The job then checks the body literally contains the substring ' - ', where is either 'stable', 'preview', or 'unstable'. Prior to this fix, the only ' - stable' marker was on the title line, which the awk script discards. The job failed with 'must declare suffix - stable to match tag parity' even though the channel was correctly declared. Add a one-line preamble in the [1.0.6] body that contains the literal substring '1.0.6 - stable'. Keeps the Keep a Changelog title format, does not pollute the actual changelog text, and documents the convention for future release bumps. --- CHANGELOG.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 44ec2b56..ba881d43 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -28,6 +28,12 @@ pour la production des paquets `.deb`. ## [1.0.6] - stable +**Release channel: 1.0.6 - stable.** The validate-release job in +`docker-publish-android.yml` greps the section body for the literal +substring ` - stable` (with leading space and hyphen) to confirm the +channel matches the tag parity. Keep this line as-is when bumping the +patch in the future. + ### Added - Self-hosted Forgejo Actions runner now drives the CI build for the yavsc repository, using the