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

Explain target variables in configured checks

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 01:23:40 +00:00
parent a3c74188be
commit d99fac23e9
2 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/consumers/adoption.md
View File

@@ -49,7 +49,12 @@ selected module to verify registration. It preserves the consumer's workspace
and toolchain settings while selecting the host for the executable. and toolchain settings while selecting the host for the executable.
For a launcher callable from other directories, first change to its consumer For a launcher callable from other directories, first change to its consumer
module directory. Follow the [CLI contract](../cli.md) for commands and exit module directory. Follow the [CLI contract](../cli.md) for commands and exit
statuses, and the [configuration reference](../config.md) for the release profile. statuses.
Configured product checks inherit the launcher's host `GOOS` and `GOARCH`.
If a check needs an application target, set it in that check's `env` map or
command. The [configuration reference](../config.md) describes
check environments and the separate target selection for built-in builds.
For consumers using vendoring, register the CLI before running `go mod vendor` For consumers using vendoring, register the CLI before running `go mod vendor`
so the vendor tree includes its dependencies. `go tool` follows Go's normal so the vendor tree includes its dependencies. `go tool` follows Go's normal

2
docs/roadmap/remediation.md
View File

@@ -119,6 +119,8 @@ the reconciliation result as well as the status.
### Explain how host normalization affects configured product checks ### Explain how host normalization affects configured product checks
**Completed.** The adoption guide explains inherited host variables and points checks that need an application target to the existing environment overlay.
**Evidence:** The updated launchers export `GOOS` and `GOARCH` to the **Evidence:** The updated launchers export `GOOS` and `GOARCH` to the
ReleaseKit process. Existing [configured checks](../config.md) inherit that ReleaseKit process. Existing [configured checks](../config.md) inherit that
process environment unless their `env` maps override it; process environment unless their `env` maps override it;