Prepare ckprompt v0.11.0 with released ckconfig
This commit is contained in:
@@ -14,14 +14,14 @@ applications.
|
||||
| `go.maximumdirect.net/ckconfig` | You want operators to view, validate, explain, and compare ConfigKit configuration. |
|
||||
| `go.maximumdirect.net/ckprompt` | You want operators to inspect PromptKit resources, check and preview requests, or run smoke tests. |
|
||||
|
||||
ckconfig v0.9.0 and ckprompt v0.10.0 select ConfigKit v1.2.1.
|
||||
ckprompt v0.10.0 selects PromptKit v0.23.2.
|
||||
ckconfig v0.10.0 and ckprompt v0.11.0 select ConfigKit v1.4.0.
|
||||
ckprompt v0.11.0 selects PromptKit v0.24.0.
|
||||
|
||||
| Selection | Core | ckconfig | ckprompt | Upstream libraries and status |
|
||||
| --- | --- | --- | --- | --- |
|
||||
| Published core | v0.7.0 | — | — | Usable independently. |
|
||||
| ConfigKit integration | v0.7.0 | v0.9.0 | — | ConfigKit v1.2.1. |
|
||||
| PromptKit integration | v0.7.0 | v0.9.0 | v0.10.0 | ConfigKit v1.2.1 and PromptKit v0.23.2. |
|
||||
| ConfigKit integration | v0.7.0 | v0.10.0 | — | ConfigKit v1.4.0. |
|
||||
| PromptKit integration | v0.7.0 | v0.10.0 | v0.11.0 | ConfigKit v1.4.0 and PromptKit v0.24.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. |
|
||||
|
||||
For applications moving from ckprompt v0.8.0, the
|
||||
@@ -34,14 +34,10 @@ Install the published core with:
|
||||
go get go.maximumdirect.net/commandkit@v0.7.0
|
||||
```
|
||||
|
||||
Select either integration with `go get go.maximumdirect.net/ckconfig@v0.9.0`
|
||||
or `go get go.maximumdirect.net/ckprompt@v0.10.0`. Both integrations select
|
||||
core v0.7.0. ckprompt v0.10.0 selects ckconfig v0.9.0, which includes
|
||||
`AdaptDiagnostics` and `ClassifyConfigurationError`. Those published releases
|
||||
build independently. The current checkout adopts
|
||||
ConfigKit v1.4.0 and PromptKit v0.24.0; ckprompt uses the new local ckconfig API
|
||||
while still requiring published ckconfig v0.9.0. Use an aligned workspace until
|
||||
ckconfig is released and selected by ckprompt.
|
||||
Select either integration with `go get go.maximumdirect.net/ckconfig@v0.10.0`
|
||||
or `go get go.maximumdirect.net/ckprompt@v0.11.0`. Both integrations select
|
||||
core v0.7.0. ckprompt v0.11.0 selects ckconfig v0.10.0, including native subtree
|
||||
scopes and path readers. These releases build independently.
|
||||
Published ckconfig v0.3.0 also uses ConfigKit v1.1.0 and does not compose with
|
||||
ckprompt v0.2.0's earlier ConfigKit dependency.
|
||||
|
||||
|
||||
@@ -119,13 +119,10 @@ If a workspace already exists, ensure it includes these three modules. Preserve
|
||||
the ignored `go.work` and `go.work.sum`; do not commit them. Use
|
||||
`GOWORK=off GOTOOLCHAIN=local` for dependency preparation
|
||||
and independent module suites. Both integrations select released core v0.7.0;
|
||||
ckprompt currently selects released ckconfig v0.9.0 but uses the new local
|
||||
ckconfig API. Until the coordinated release, isolated validation uses a temporary
|
||||
local replacement as described in the [implementation plan](roadmap/implementation.md#stage-7-validate-the-result-and-record-release-coordination);
|
||||
the independent suite against published requirements remains pending.
|
||||
The aligned workspace exercises local sources together. Run the independent
|
||||
suites for core and ckconfig with `GOWORK=off GOTOOLCHAIN=local go test ./...`
|
||||
from each module directory. From the repository root, a workspace containing
|
||||
ckprompt selects released ckconfig v0.10.0. All three modules support independent
|
||||
builds against their published dependencies. Run each independent suite with
|
||||
`GOWORK=off GOTOOLCHAIN=local go test ./...` from its module directory.
|
||||
The aligned workspace exercises local sources together. From the root,
|
||||
all three modules can also run:
|
||||
|
||||
```sh
|
||||
|
||||
Reference in New Issue
Block a user