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

Update ReleaseKit documentation and attribution

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 03:02:16 +00:00
parent eb974b6d29
commit bdc3fd8fa3
6 changed files with 23 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/roadmap/release-simplification.md
View File

@@ -3,8 +3,9 @@
Status: the selected release-tooling design has been implemented. All four
generic file checks, registered-tool execution, page-only hosted delivery, and
protection of the supplied token path are selected.
The [implementation plan](implementation.md) owns stage order, tasks, validation,
and completion evidence. Current release behavior stays with its canonical owners.
The [completed implementation record](https://forge.maximumdirect.net/base-layer/commandkit/src/commit/87eb84ccb462bf54e6250c8b287ac217efe90883/docs/roadmap/implementation.md)
contains stage order, tasks, validation, and completion evidence. Current release
behavior stays with its canonical owners.
## Purpose and authority
@@ -93,8 +94,8 @@ identity from a current profile. Keep the existing publication interface and
provide an explicit delivery invocation without automatically chaining the two
operations. Keep one selector mapping and shared invocation plumbing.
A pending upstream request concerns host-safe consumer launcher examples and
regression coverage. It is not a dependency of this work: v0.8.0 already supports
ReleaseKit v0.9.0 shipped host-safe consumer launcher examples and regression
coverage. The earlier simplification used v0.8.0, which already supported
registered tools. Keep host normalization locally because the reviewed
`go tool` invocation inherited foreign `GOOS`/`GOARCH` values and failed to run.
Do not switch tool-version selection from the root module to each integration