From 7416bf6fdc29998e820969ea45e856912afb78cd Mon Sep 17 00:00:00 2001 From: Eric Rakestraw Date: Sat, 7 Nov 2026 05:08:12 +0000 Subject: [PATCH] Prepare the core release candidate --- docs/releases/v0.4.0.md | 32 ++++++++++++++++++++++++++++++++ docs/roadmap/implementation.md | 5 +++++ 2 files changed, 37 insertions(+) create mode 100644 docs/releases/v0.4.0.md diff --git a/docs/releases/v0.4.0.md b/docs/releases/v0.4.0.md new file mode 100644 index 0000000..2e4f9c0 --- /dev/null +++ b/docs/releases/v0.4.0.md @@ -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) diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index 7e24587..80e9617 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -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