CLI release process
Release the native executable independently of template instructions.
Prepare the release
On a branch from release/X.Y, set CLI_VERSION and draft the release request:
sh scripts/release-notes.sh cli 2.5.1The script writes release/requests/cli/2.5.1.md from every CLI change file under .changelog/, under the headings Upgrade notes, Breaking, Added, Fixed, Changed, and Contributors, each entry linking its pull request as #N. Edit the draft as freely as a request written by hand: a release note describes the difference from the previous release a user had, not the pull requests in between. A stable release's draft removes the change files it used; a candidate's leaves them for the stable release. The template's VERSION need not change unless its own product changes.
Build and validate
gofmt -l .
sh scripts/check-release.sh "$(mktemp -d)/out"gofmt -l . prints nothing when the Go files are formatted. check-release.sh runs go test ./... and go vet ./..., then builds both products and runs the publication, version, and release-note checks. Its output directory must not exist yet.
Release archives cover macOS, Linux, and Windows on amd64 and arm64. They include checksums and the Apache-2.0 license. Installer verification checks both the archive checksum and the embedded executable version. scripts/release-version.sh cli prints the version the CLI builds as: CLI_VERSION in a public checkout, or <base>-<label>.<counter> in a variant fork.
Publish from the release branch
Open the release-prep pull request into release/X.Y. Merging it runs Publish there, which is the maintainer's explicit act: the gate job runs native tests, then the cli job creates the cli-v* release when CLI_VERSION names a version not yet out, before the template job. A version already released is left alone.
Cross-compilation is build evidence, not proof of native installer or filesystem behavior. Native CI exercises each operating system. See validation and tests.