diff --git a/docs/consumers/guide.md b/docs/consumers/guide.md index 0a92102..8adcdc0 100644 --- a/docs/consumers/guide.md +++ b/docs/consumers/guide.md @@ -24,7 +24,7 @@ core-only, ConfigKit-only, and composed applications. ## Go compatibility All three modules declare a consumer minimum of Go 1.26.0. The root module also -selects ReleaseKit v0.8.0 (`go.maximumdirect.net/releasekit`) as a Go tool, which +selects ReleaseKit v0.9.0 (`go.maximumdirect.net/releasekit`) as a Go tool, which makes that tool's module graph part of the root consumer module requirements even though production packages do not import ReleaseKit. The [release policy](../policy/release.md#consumer-minimum-and-release-toolchain) diff --git a/docs/oss/attribution.md b/docs/oss/attribution.md index a13e56b..ba1abf1 100644 --- a/docs/oss/attribution.md +++ b/docs/oss/attribution.md @@ -139,16 +139,16 @@ License and notices: [CC BY-SA 4.0](licenses/CC-BY-SA-4.0.txt) | ## ReleaseKit -Selected module: `go.maximumdirect.net/releasekit` at `v0.8.0` (selected Go tool; not a runtime import). +Selected module: `go.maximumdirect.net/releasekit` at `v0.9.0` (selected Go tool; not a runtime import). Copyright (C) 2026 Eric Rakestraw SPDX-License-Identifier: LGPL-3.0-or-later License and notices: [LGPL v3.0](../../LICENSE) | -[LICENSE](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/LICENSE). +[LICENSE](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/LICENSE). -[Source](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f). +[Source](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4). ## Goldmark diff --git a/docs/policy/release.md b/docs/policy/release.md index b2393cf..f1d99a6 100644 --- a/docs/policy/release.md +++ b/docs/policy/release.md @@ -25,7 +25,7 @@ additional release requirements. CommandKit independently versions three source-only Go modules: the root core, `integrations/ckconfig`, and `integrations/ckprompt`. Standard CLI behavior is exposed by consuming applications; CommandKit does not declare binary -deliverables or a cross-platform build matrix. ReleaseKit v0.8.0 is selected as +deliverables or a cross-platform build matrix. ReleaseKit v0.9.0 is selected as the maintainer publication tool. Maintainers may separately deliver page-only Gitea releases from tagged source; delivery has its own outcome and URL. The [release procedure](../release.md) owns the selected-module workflow, release diff --git a/docs/release.md b/docs/release.md index a1c7faf..980b1f2 100644 --- a/docs/release.md +++ b/docs/release.md @@ -22,13 +22,13 @@ module profile enforces the endpoint. The maintainer needs the selected This procedure follows the [release policy](policy/release.md); release-note footers follow the [OSS discoverability policy](policy/oss.md#discoverability). -ReleaseKit v0.8.0 (`go.maximumdirect.net/releasekit`) owns candidate validation, +ReleaseKit v0.9.0 (`go.maximumdirect.net/releasekit`) owns candidate validation, publication guards, tag creation, tag publication, and outcome reporting. Its pinned public contracts are the -[CLI reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/cli.md), -[profile reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/config.md), -the [publication guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/consumers/publish.md), -and the [delivery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/consumers/delivery.md). +[CLI reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/cli.md), +[profile reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/config.md), +the [publication guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/consumers/publish.md), +and the [delivery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/consumers/delivery.md). The repository selects one default module suite per invocation. The launcher uses the root module’s registered tool with native host settings and read-only module metadata. @@ -78,7 +78,7 @@ integration directory. Future tag URLs need not resolve before publication. All three release profiles explicitly select the repository-root `COPYRIGHT`, `LICENSE`, and `docs/oss/attribution.md` through `validation.shared_files`. ReleaseKit requires these committed files to exist in the candidate. The list -does not expand Go validation scope; see the pinned [profile reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/config.md). +does not expand Go validation scope; see the pinned [profile reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/config.md). Each integration also distributes its own `COPYRIGHT`, `LICENSE`, and `docs/oss/attribution.md`. These module-local materials are separate from the @@ -156,9 +156,9 @@ Reconciliation observes the recorded endpoint, full tag, and tag object without rerunning candidate validation or changing tags. It distinguishes confirmed publication, current absence, conflict, and an unresolved observation. Current absence does not prove that a version was never published. The pinned -[CLI reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/cli.md#recover-a-saved-publication-attempt-or-discover-local-attempts) +[CLI reference](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/cli.md#recover-a-saved-publication-attempt-or-discover-local-attempts) owns recovery statuses and structured output; the -[publication guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/consumers/publish.md#retain-and-reconcile-publication-evidence) +[publication guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/consumers/publish.md#retain-and-reconcile-publication-evidence) describes record storage and recovery entry points. If no usable record was saved, use the exact endpoint, full tag, and annotated @@ -188,7 +188,7 @@ worktree and index, then deliver the selected module's page: The profile derives the full module-specific tag from the version. Delivery uses the checked-in release note as a page-only body and reports its own outcome and URL separately from source publication. Retry later from the same original -tagged source. The pinned [delivery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/23203f235cc414c4ffe0fd3941030eb0c9f9943f/docs/consumers/delivery.md) +tagged source. The pinned [delivery guide](https://forge.maximumdirect.net/base-layer/releasekit/src/commit/2180aa868ec2caa95fc8279fd59d5f0ebac41bd4/docs/consumers/delivery.md) owns delivery and retry behavior. A nonblank `RELEASEKIT_GITEA_TOKEN` takes precedence over the repository-relative diff --git a/docs/roadmap/implementation.md b/docs/roadmap/implementation.md index edda4b8..8d0a6a5 100644 --- a/docs/roadmap/implementation.md +++ b/docs/roadmap/implementation.md @@ -1,6 +1,6 @@ # ReleaseKit v0.9.0 implementation plan -Status: Stages 1–2 complete; Stages 3–6 are not started. +Status: Stages 1–3 complete; Stages 4–6 are not started. Implement these stages in integer order during one end-to-end sprint. The target audience is the Luna coding agent. Intermediate stages may temporarily leave @@ -139,7 +139,9 @@ and complete the source checks in Stages 4 and 5 before committing that unit. ## Stage 3: Align current documentation and attribution -**Status:** not started. +**Completed.** Current tool references and attribution now identify v0.9.0 and +its pinned source. Upstream COPYRIGHT and LICENSE are unchanged; affected local +links and pinned upstream paths and recovery fragments were checked. Update these owners together with the tool adoption: diff --git a/docs/roadmap/release-simplification.md b/docs/roadmap/release-simplification.md index 00f3f40..ab34016 100644 --- a/docs/roadmap/release-simplification.md +++ b/docs/roadmap/release-simplification.md @@ -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