Select the ConfigKit upgrade toolchain and dependencies

This commit is contained in:
2026-11-17 20:39:48 +00:00
parent 79088a3546
commit ae0e410875
4 changed files with 12 additions and 4 deletions

View File

@@ -8,16 +8,16 @@ for development, and Windows is unsupported. `main` on `origin` is authoritative
## Prepare
Use Git, a POSIX shell, and a Go installation supporting toolchain selection.
The selected release toolchain is Go 1.25.5. Select it for candidate validation
The selected release toolchain is Go 1.27.0. Select it for candidate validation
and release builds, including any CI performing those tasks:
```sh
export GOTOOLCHAIN=go1.25.5
export GOTOOLCHAIN=go1.27.0
go version
```
The consumer minimum is declared in [`go.mod`](../go.mod). Its patch-level
minimum is required by the selected PromptKit dependency. Selecting a newer
minimum is required by the selected ConfigKit dependency. Selecting a newer
release toolchain is a separate runbook update and leaves that minimum unchanged.
Configure ordinary Git credentials for `origin` and private-module access

View File

@@ -121,6 +121,11 @@ semantics. No new resource-existence or access policy is introduced.
## Stage 1 — Select The Mixed Dependency Graph And Toolchain
**Complete.** Go 1.27.0 was verified using the locally installed toolchain;
both ConfigKit packages build with YAML v4.0.0-rc.6, and the existing config,
CLI, and LLM packages compile with the selected graph. Application API migration
and full behavioral checks remain in their respective stages.
Goal: establish the approved build inputs without migrating PromptKit.
Inspect `go.mod`, `go.sum`, pinned ConfigKit/PromptKit module files, the v1.2.0