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

13
docs/roadmap/releasekit.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit Adoption Roadmap
Status: Adoption scope agreed; implementation has not started.
Status: Tool dependency selected; remaining adoption work is pending.
The [implementation plan](implementation.md) owns the ordered migration steps.
## Purpose
@@ -71,10 +71,13 @@ push result. Tool bootstrap and dependency preparation precede offline
candidate validation. The wrapper's responsibility is tool invocation;
ReleaseKit owns candidate guards, validation coordination, tags, and recovery.
Release preparation advances PromptKit's `go.mod` Go requirement to the latest
Go version available in the development environment. The
Release preparation records the initial stable release of the latest locally
available Go series as PromptKit's minimum requirement, retaining a higher patch
minimum where needed by a dependency or a specific correctness fix. The
[runbook preparation step](../release.md#prepare-the-candidate) makes that
toolchain active before committing the candidate. Use the same Go version
series' latest locally available patch active before committing the candidate.
The module minimum and build toolchain are separate: for example, `go 1.26.0`
can be built and validated with Go 1.26.8. Use the same local Go version
to build ReleaseKit and run PromptKit's release validation, including the
consumer examples. Local tooling uses that selected installation rather than
an executable previously built with a different Go version or an automatically
@@ -203,7 +206,7 @@ Update the affected canonical owners when the implementation lands:
| --- | --- |
| `docs/policy/release.md` | Describe the shared validation selections, simpler note convention, adopted publication/recovery model, retired gates, and selected deliverables. Preserve the Go-update/same-toolchain requirement, existing compatibility policy, and catalog-profile policy. |
| `docs/policy/testing.md` | Route release validation through ReleaseKit while retaining race, full vet, and the three consumer workflows. Distinguish ordinary development checks from committed-candidate validation. |
| `docs/release.md` | Preserve the preparation-time update to the latest development-environment Go version; document building ReleaseKit with that same toolchain, dependency preparation, one publication command, and upstream recovery. |
| `docs/release.md` | Preserve the preparation-time series-based Go minimum and latest-local-patch selection; document building ReleaseKit with that same toolchain, dependency preparation, one publication command, and upstream recovery. |
| `docs/development.md` | Replace the old checker inventory and prerequisites with current tool ownership and focused development commands. |
| `docs/oss/attribution.md` and related notices, if applicable | Apply the OSS policy to the selected tooling and any copied or adapted material according to actual use and distribution. Tool use alone is not a blanket attribution requirement. |