base-layer/promptkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

Clarify local Go toolchain selection

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-05 13:39:31 +00:00
parent 6a1a32ae49
commit 4ec35f5ca6
2 changed files with 13 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/development.md
View File

@@ -58,6 +58,14 @@ exist.
## Maintainer Validation
Use the newest Go installation already available locally for ordinary
development checks. Put its `bin` directory first on `PATH` and set
`GOTOOLCHAIN=local` to keep that toolchain selected. For repository-isolated
checks, set `GOWORK=off`; consumers may use their own workspaces. The selected
validation patch does not by itself change the module's consumer minimum. See
the [release toolchain policy](policy/release.md#consumer-minimum-and-release-toolchain)
and [release procedure](release.md#prepare-the-candidate) for release selection.
For ordinary work, select validation proportionate to the change. Do not repeat
successful checks for unchanged content merely to create a commit. During
development, run relevant Go tests and vet, format changed Go files, and execute

5
docs/roadmap/implementation.md
View File

@@ -67,6 +67,11 @@ authorize pushing, tagging, publishing, or selecting a release version.
No new installation, vulnerability gate, consumer advisory, or dependency update
is needed for the assessed environment.
Completion: selected the locally available Go 1.27.3 toolchain (`go version
go1.27.3 linux/amd64`) with `GOTOOLCHAIN=local` and `GOWORK=off` for isolated
validation. The module minimum remains Go 1.27.0; contributor guidance now
describes local toolchain selection.
## Stage 2: Remove Convenience Source Conversion
**Catalog:** 3, 5. **Files:** `profiles.go`, `backends.go`, `provider_values.go`,