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

Prepare ckconfig v0.5.0 with released core dependencies

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-08 00:31:21 +00:00
parent 49f2d09ccd
commit 5c96053255
4 changed files with 45 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/consumers/guide.md
View File

@@ -18,7 +18,7 @@ The following distinguishes published combinations from the current checkout:
| Selection | Core | ckconfig | ckprompt | Upstream libraries and status |
| --- | --- | --- | --- | --- |
| Published core | v0.4.0 | — | — | Usable independently. |
| Published core | v0.5.0 | — | — | Usable independently. |
| Published ConfigKit integration | v0.4.0 | v0.4.0 | — | ConfigKit v1.1.0. |
| Earlier matched integration set | v0.3.0 | v0.2.0 | v0.2.0 | ConfigKit v0.8.0 and PromptKit v0.16.0, using their earlier import paths. |
| Current source | Local | Local | Local | ConfigKit v1.1.0 and PromptKit v0.20.0; use an aligned workspace until release dependencies are updated. |
@@ -26,10 +26,10 @@ The following distinguishes published combinations from the current checkout:
Install the published core with:
```sh
go get go.maximumdirect.net/commandkit@v0.4.0
go get go.maximumdirect.net/commandkit@v0.5.0
```
Core v0.5.0 and ckprompt v0.3.0 have unpublished candidate notes. Current
The integration releases being prepared are ckconfig v0.5.0 and ckprompt v0.5.0. Current
ckprompt source calls `ckconfig.AdaptDiagnostics`, which is absent from its
selected released ckconfig v0.4.0 dependency. It therefore needs local
ckconfig source in the workspace until [release