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

Record ckconfig release completion

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-04 16:17:49 +00:00
parent bc1d1d5844
commit eeae10fa05
5 changed files with 9 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/consumers/guide.md
View File

@@ -16,7 +16,7 @@ installed at the application root, not as group children.
| `go.maximumdirect.net/ckprompt` | The application wants PromptKit engine configuration/comparison, five catalogs, named inspection, requirements discovery, request validation, or native smoke testing. |
The published matched releases are core v0.3.0, ckconfig v0.2.0, and ckprompt v0.2.0.
The local ckconfig v0.3.0 candidate uses ConfigKit v1.1.0 and does not compose
The published ckconfig v0.3.0 uses ConfigKit v1.1.0 and does not compose
with ckprompt v0.2.0, which retains ckconfig v0.2.0 and ConfigKit v0.8.0.
Update application imports and dependency versions together; old and new core
paths have distinct Go type identities. Install core with
@@ -32,8 +32,8 @@ core-only, ConfigKit-only, and composed applications.
## Go compatibility
Core and ckprompt declare a consumer minimum of Go 1.26.0; the ckconfig
v0.3.0 candidate requires Go 1.27.0. The root module also
Core and ckprompt declare a consumer minimum of Go 1.26.0; ckconfig
v0.3.0 requires Go 1.27.0. The root module also
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
@@ -358,7 +358,7 @@ and [PromptKit v0.16.0 consumer guidance](https://gitea.maximumdirect.net/eric/p
## ConfigKit v1.1 migration
The ckconfig v0.3.0 candidate uses `go.maximumdirect.net/configkit v1.1.0`
Ckconfig v0.3.0 uses `go.maximumdirect.net/configkit v1.1.0`
and Go 1.27.0. Consumers must migrate ConfigKit imports and values passed to
ckconfig: the old and new package paths have distinct type identities. Source
reports rename `destination_unresolved` to `destination_is_fallback` and

11
docs/roadmap/future.md
View File

@@ -21,17 +21,6 @@ an idea here does not select its syntax, API, priority, or delivery date.
## Pending release and integration work
### ckconfig release and hosted delivery
The ckconfig v0.3.0 candidate adopts ConfigKit v1.1.0 and Go 1.27.0; its
implementation and audits are complete. Its
[candidate release note](../../integrations/ckconfig/docs/releases/v0.3.0.md)
is prepared, but source publication and hosted delivery remain pending. Complete
those operations when requested through the [release procedure](../release.md),
using the existing fresh-version guards and reporting source publication and
hosted Gitea delivery separately. Publishing this roadmap cleanup does not
publish a module version tag or deliver a release page.
### ckprompt dependency migration and workspace alignment
Review the upstream PromptKit vanity release and select compatible ConfigKit