From 40f8a1c6283ff449a56f7c80e2744be90384c6f3 Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Tue, 28 Jul 2026 15:59:23 -0500 Subject: [PATCH] Identify v0.12.0 as the first published application-only release --- docs/release.md | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-) diff --git a/docs/release.md b/docs/release.md index a165392..37ae9f4 100644 --- a/docs/release.md +++ b/docs/release.md @@ -8,11 +8,11 @@ releases. The hosted executables, publishes their SHA-256 checksums, and uses the matching file under `docs/releases/` as the hosted release body. -`v0.12.0` is the selected version for the pending first application-only -release. It remains an unreleased candidate until its annotated tag is -published, the hosted workflow succeeds, and every published artifact is -verified. Later releases select a new `vMAJOR.MINOR.PATCH` version according to -the intended compatibility change. +`v0.12.0` is the first published application-only release. For each later +release, select a new `vMAJOR.MINOR.PATCH` version according to the intended +compatibility change. A selected version remains an unreleased candidate until +its annotated tag is published, the hosted workflow succeeds, and every +published artifact is verified. Run this procedure from the Scriptorium repository root. A release must not depend on a Go workspace, module replacement, vendor tree, sibling checkout, @@ -20,14 +20,17 @@ unpublished dependency, or unpushed source commit. ## Establish The Candidate -For the pending application-only release, start a POSIX shell and select: +Start a POSIX shell, choose a semantic version that has not been published, and +export it as `RELEASE_VERSION`. For example, if `v0.12.1` is the intended next +version and remains unpublished, select: ```sh -export RELEASE_VERSION=v0.12.0 +export RELEASE_VERSION=v0.12.1 ``` -For a later release, export its not-yet-published semantic version instead. -Then run the following guard in that same shell: +Use the version appropriate to the actual compatibility change rather than +assuming that the example is the next release. Then run the following guard in +that same shell: ```sh set -eu