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

Separate the Go minimum from the release toolchain

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 16:14:50 +00:00
parent 3ca01ae0b0
commit 1889915a81
5 changed files with 47 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/release.md
View File

@@ -11,16 +11,22 @@ Required tools are Git, Go with race-detector support, POSIX shell, and Python
Use the latest Go toolchain available in the development environment for
release preparation and validation. Make that installation the active `go`
command, then advance PromptKit's Go requirement before committing the
candidate:
command, then advance PromptKit's minimum Go requirement to that series' first
stable release before committing the candidate:
```sh
export GOTOOLCHAIN=local
go version
release_go_version=$(go env GOVERSION)
go get "go@${release_go_version#go}"
release_go_series=${release_go_version#go}
release_go_series=${release_go_series%.*}
go mod edit "-go=${release_go_series}.0"
```
For example, building with Go 1.26.8 normally records `go 1.26.0`, not
`go 1.26.8`. If a dependency or a specific correctness fix requires a higher
patch minimum, use that minimum instead of reducing it to `.0`.
Include the module change in the candidate commit. Describe a raised minimum
Go requirement in the release note and select the release version under the
[compatibility policy](policy/release.md#versioning-and-compatibility).