eric/ReleaseKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

Separate the Go minimum from the release build toolchain

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 16:29:48 +00:00
parent d51a0ada5e
commit 4bb480f990
5 changed files with 67 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
docs/policy/release.md
View File

@@ -2,7 +2,7 @@
**Base Policy Version:** 1.4
**Last Updated**: 2026-10-07
**Last Updated**: 2026-10-08
**Upstream Source:** [release.md](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md)
@@ -81,6 +81,35 @@ Additional compatibility promises and deliberate exceptions belong in the
adopted policy or canonical contract documentation. Release notes explain
changes; they do not redefine current compatibility contracts.
## Go Minimum And Release Toolchain
ReleaseKit provides reasonable support for routine build and release needs,
following [ADR 0002](../adr/0002-routine-releases.md). Its Go support policy relies
on upstream compatibility commitments and verification proportionate to those
needs.
Select the Go series during release preparation. When advancing the consumer
minimum, use the latest locally available stable series and record its initial
stable version in `go.mod`, such as `go 1.26.0`. Use a higher patch minimum when
a dependency requirement or identified correctness fix requires it. Minimum
increases follow the versioning and compatibility rules above and are explained
in the release note.
Build the maintainer release executable and validate the candidate with the
same latest locally available patch of the selected series. Keep that toolchain
active throughout preparation, tool bootstrap, and validation, using local
toolchain selection. Maintained CI images follow the chosen build toolchain.
The patch used for these operations is separate from the consumer minimum.
Successful build and release validation on that patch serve as sufficient
evidence of support from the series' initial stable release through subsequent
patch releases, subject to known dependency requirements or correctness issues.
This relies on Go's [release policy](https://go.dev/doc/devel/release#policy) and
[compatibility commitments](https://go.dev/doc/go1compat). Additional
patch-specific validation is warranted by concrete evidence; routine releases
require no patch-version matrix. Record the actual validation toolchain in the
release evidence.
## Release Documentation And Preparation
Every new release must include `docs/releases/<version>.md` in the tagged