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

17
docs/policy/release.md
View File

@@ -210,12 +210,17 @@ annotated stable SemVer tags. It has no binaries, hosted download pages, or
asynchronous deliverables. The source commit is pushed through main before the
tag. The [release procedure](../release.md) owns commands and recovery.
Release preparation advances Promptkit's `go.mod` Go requirement to the latest
Go version available in the development environment. Use that same toolchain
for candidate validation and to build any maintainer release executable.
Commit the module update before validating the final candidate, and describe
the resulting minimum Go requirement and compatibility impact in the release
note under the versioning policy above.
Release preparation advances Promptkit's `go.mod` Go requirement to the initial
stable release of the latest Go series available in the development environment
(for example, `go 1.26.0`). Use a higher patch minimum when required by a
dependency or a specific correctness fix, rather than recording the maintainer's
current patch solely because it was used to build the release.
Use the latest locally available patch in that series for candidate validation
and to build any maintainer release executable. Keep that same local toolchain
active throughout those operations. Commit the module update before validating
the final candidate, and describe a raised minimum Go requirement and its
compatibility impact in the release note under the versioning policy above.
The existing publication script requires Summary, Compatibility, Upgrade, and
Changes headings beneath a title of `# Promptkit vMAJOR.MINOR.PATCH`. State