From 9d34a534a2a84e9c5badad254606b3f83407e8a3 Mon Sep 17 00:00:00 2001 From: 777genius Date: Sun, 24 May 2026 15:57:36 +0300 Subject: [PATCH] docs(release): require release notes closeout - Add a required release closeout gate before a release is considered finished. - Require user-facing notes, current Downloads links and gh release verification. --- docs/RELEASE.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/RELEASE.md b/docs/RELEASE.md index acef573b..21f47455 100644 --- a/docs/RELEASE.md +++ b/docs/RELEASE.md @@ -131,6 +131,18 @@ EOF )" ``` +### 4. Required release closeout gate + +Do not publish or call a release finished until this is true: + +- The GitHub release body is not just auto-generated `Full Changelog`. +- The release body starts with short user-facing notes: what changed, why users care, and the most important fixes. +- The `Downloads` table from the template is present and every link points to the current `v` assets. +- The asset names in the notes match the assets uploaded by `release.yml`. +- `gh release view v --json body,assets,isDraft,isPrerelease` confirms the release is public, has notes, and has the expected installer assets. + +If a draft was published before notes were written, immediately edit the public release body with `gh release edit`; do not leave a release with only generated notes. + ## Release Notes Template ```markdown