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

Clarify the recovery command target scope

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 01:21:28 +00:00
parent fcec6357ff
commit b00bc41b65
2 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
docs/cli.md
View File

@@ -154,8 +154,9 @@ uses a persistent native executable when available. Recognized temporary Go-buil
executables provide no native fallback after their driver exits. Command
preparation has its own bounded context after a failed publication, so publication
cancellation permits preparing the later invocation. Each entry point preserves
the recovery exit status. Generated Go-tool handoffs select the host target when
they run, independently of inherited cross-compilation settings.
the recovery exit status. Run a generated Go-tool handoff in a POSIX shell.
When it runs, it sets `GOOS` and `GOARCH` to the selected Go toolchain's
`GOHOSTOS` and `GOHOSTARCH`.
If the selected entry point becomes unavailable, use another supported ReleaseKit
CLI with the saved record.

2
docs/roadmap/remediation.md
View File

@@ -28,6 +28,8 @@ published instructions from a newly created file under a foreign target.
## Limit the recovery guarantee to GOOS and GOARCH
**Completed.** The CLI reference names the two target variables and identifies the shell syntax.
**Evidence:** The [CLI contract](../cli.md) says Go handoffs select the host
“independently of inherited cross-compilation settings.” The
[command formatter](../../cmd/releasekit/main.go) overrides `GOOS` and