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

Clarify release command exit statuses

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 17:08:35 +00:00
parent 84b59c690d
commit b1ecd9a078
2 changed files with 9 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/release.md
View File

@@ -81,11 +81,11 @@ go list -m gitea.maximumdirect.net/eric/ReleaseKit
"$releasekit_bin" version
```
The module-selected executable is ReleaseKit v0.2.0. Do not use `go run` or
`go tool` for publication: the native executable preserves its exit status and
the publication-state diagnostics. ReleaseKit's child Go commands use the
`go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected executable
first on `PATH` through the publication command.
The module-selected executable is ReleaseKit v0.2.0. Use the built executable
for publication to preserve its exit status and publication-state diagnostics.
`go run` maps a nonzero child exit status to 1. ReleaseKit's child Go commands
use the `go` found on `PATH` with `GOTOOLCHAIN=local`; keep the selected
executable first on `PATH` through the publication command.
Verify access to the authoritative remote without displaying credentials:

4
docs/roadmap/remediation.md
View File

@@ -43,6 +43,10 @@ gate or ConfigKit-owned recovery implementation.
## 2. Remove the unsupported prohibition on `go tool` (P3)
Status: Complete. The runbook retains the built-executable workflow and limits
its exit-status explanation to `go run`. A fresh `go tool` check preserved
ReleaseKit's status 2 and publication diagnostics.
Affected: [release procedure](../release.md#1-select-go-and-prepare-the-tool),
lines 84–86.