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

Prepare the initial CommandKit release note

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-09 04:07:52 +00:00
parent 54750dd957
commit 9ee6ca43ef
2 changed files with 62 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/roadmap/deferred.md
View File

@@ -79,7 +79,7 @@ target. Reconsider them only with concrete motivation and review of ownership,
invocation state, native reports, and the affected contracts. Retained measurement
records are historical evidence, not performance guarantees or release gates.
## Consumer adoption and release preparation
## Consumer adoption
Consumer migrations remain separate from library delivery. Applications can
replace duplicated standard handlers and routing, then update their CLI docs
@@ -87,8 +87,3 @@ and subprocess consumers for intentional changes while retaining domain commands
No migration order or claim about individual applications' adoption is recorded
here; the [consumer guide](../consumers/guide.md) and maintained examples provide
integration guidance.
The next CommandKit release note must explain the Go 1.26.0 minimum and the
consumer action required by the ReleaseKit v0.3.0 upgrade. Version selection,
matching notes, and publication follow the [maintainer procedure](../release.md).
This cleanup does not select a release version or publish a release.