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

Align the release policy with Go compatibility guidance

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-09 03:45:39 +00:00
parent eae21797f7
commit dc0adf5751
4 changed files with 91 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
docs/release.md
View File

@@ -12,12 +12,17 @@ Required tools are Git, Go with race-detector support, POSIX shell, and Python
Use the latest Go installation available locally for the release tool, the
candidate validation, and the maintained examples. Make it the active `go`
command and record its version. Set Promptkit's consumer minimum to the initial
stable release of that Go series before committing the candidate:
command and record its version:
```sh
export GOTOOLCHAIN=local
go version
```
For a minor release, advance Promptkit's consumer minimum to the initial stable
release of that Go series before committing the candidate:
```sh
release_go_version=$(go env GOVERSION)
release_go_series=${release_go_version#go}
release_go_series=${release_go_series%.*}
@@ -25,9 +30,14 @@ go mod edit "-go=${release_go_series}.0"
```
For example, Go 1.26.8 normally results in `go 1.26.0`. Keep a higher patch
minimum if a dependency or correctness fix requires it. Prepare module caches
before validation; this may update `go.sum` and belongs before the candidate
commit:
minimum if a dependency or identified correctness fix requires it. For a patch
release, leave the consumer minimum unchanged; using a newer validation
toolchain does not itself raise that minimum. If the candidate needs a higher
minimum, prepare a minor release instead. See the
[consumer-minimum policy](policy/release.md#consumer-minimum-and-release-toolchain).
Prepare module caches before validation; this may update `go.sum` and belongs
before the candidate commit:
```sh
GOTOOLCHAIN=local go mod download