docs(release-process): per-release authorization gate + pre-tag changelog reconcile#56
Conversation
…elog reconcile Two failure modes from a live release session: - Release authorization is per-release: a finished feature cycle (or a 'fix these issues' task) does not authorize cutting or even staging a release. Staging counts — a bumped, auto-merged release PR is a release the user did not ask for. - Position is not content: the mandatory pre-tag HEAD==tip check proves where the tag lands, not that the CHANGELOG describes it. Parallel PRs merging after the release PR ship undocumented unless the changelog is reconciled against git log vPREVIOUS..HEAD immediately before tagging. Bump skill version 0.8.4 -> 0.8.5. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
github-actions
Bot
added
documentation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the release process documentation to emphasize that release authorization is required per-release and to introduce a step for reconciling the CHANGELOG against the git history before tagging. It also bumps the skill version to 0.8.5. The feedback suggests replacing the placeholder 'vPREVIOUS' with '<prev_tag>' in the git command to prevent potential confusion with double 'v' prefixes.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
…le example Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
|
From a retrospective on a live multi-release session.
Two additions to
release-process.mdRelease authorization is per-release (Phase 1, Issue Gate area). A finished feature cycle does not authorize cutting or staging a release; authorization does not carry forward from a prior release, and "fix these issues / finish this PR" never authorizes one. The autonomous pipeline ends at merged PRs + green CI + closed issues, then stops and reports "release-ready". Staging counts as releasing — a bumped, auto-merged release PR is a release the user didn't ask for ("Did you release? I wasn't asking for a release.").
Position is not content (Phase 3). The existing mandatory pre-tag
HEAD == remote tipcheck proves where the tag lands, not that the CHANGELOG describes what it contains. Parallel PRs can merge onto main between release-PR prep and tag time; tagging then ships them undocumented. Adds a pre-tag reconcile step: diffgit log --first-parent vPREVIOUS..HEADagainst the[X.Y.Z]section and document anything missing before tagging.Skill version 0.8.4 → 0.8.5. Docs-only.