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

Prepare the core release candidate

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-07 05:08:12 +00:00
parent d14fa366f5
commit 7416bf6fdc
2 changed files with 37 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

32
docs/releases/v0.4.0.md Normal file
View File

@@ -0,0 +1,32 @@
# CommandKit v0.4.0
CommandKit v0.4.0 adds shared structured reporting and reusable CLI input
facilities. Applications and integrations can submit one report value for
automatic or explicit text, YAML, and JSON output. Core selects the format,
renders optional standard text templates, and records presentation failures
through the existing invocation lifecycle. The writer API exposes the same
rendering behavior outside an invocation.
Report values use JSON serialization conventions for structured output. The
safe YAML conversion helper accepts upstream inspection documents without
reconstructing configuration or treating ordinary strings as YAML. Public CLI
JSON parsing and ordered flag occurrences support structured inputs and
interleaved bindings. Applications can reuse and rename flag bindings while
preserving their typed parsing and presence behavior.
This pre-1.0 minor release reserves the long flag `--format` for core and
changes standard version output to use shared reporting. Applications that
declare a local `--format` must remove or rename it; an application alias may
target the core flag. Integration report framing and format availability have
changed with the shared API; select compatible integration releases as they
become available. See the [CLI reference](../cli.md#reporting) and
[consumer guide](../consumers/guide.md#invocation-reporting) for current
contracts and examples.
Core continues to declare a Go 1.26.0 consumer minimum. The maintainer release
toolchain is Go 1.27.0, and core has no ConfigKit or PromptKit integration
dependency.
[COPYRIGHT](https://forge.maximumdirect.net/base-layer/commandkit/src/tag/v0.4.0/COPYRIGHT) |
[LICENSE](https://forge.maximumdirect.net/base-layer/commandkit/src/tag/v0.4.0/LICENSE) |
[ATTRIBUTION](https://forge.maximumdirect.net/base-layer/commandkit/src/tag/v0.4.0/docs/oss/attribution.md)

5
docs/roadmap/implementation.md
View File

@@ -869,6 +869,11 @@ bootstrap work enters this sprint.
## Stage 24: Core release candidate and publication handoff
**Candidate preparation.** On 2026-11-07 the authoritative `origin` had no
core `v0.4.0`, ckconfig `v0.4.0`, or ckprompt `v0.3.0` tag; local tags also
did not contain those versions. Core `v0.4.0` is the selected candidate. Its
source publication and the dependent integration releases remain pending.
Inspect authoritative release state under the [release procedure](../release.md)
before selecting versions. Use the next unused core minor release (expected
v0.4.0 if still unused), a later ckconfig minor release (expected v0.4.0), and