Document configuration outcomes and release handoff
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# Future work
|
||||
|
||||
Status: optional shell validation and future capability proposals.
|
||||
Status: release coordination, optional shell validation, and future capability proposals.
|
||||
No delivery dates are selected here.
|
||||
|
||||
## Purpose and authority
|
||||
@@ -30,6 +30,24 @@ govern any future implementation. The [CLI reference](../cli.md), public GoDoc,
|
||||
and [consumer guide](../consumers/guide.md) own implemented behavior. Retaining
|
||||
an idea here does not select its syntax, API, priority, or delivery date.
|
||||
|
||||
## Configuration outcome release handoff
|
||||
|
||||
The current ckprompt source requires the classifier in local ckconfig, while
|
||||
its published dependency remains ckconfig v0.7.0. The aligned workspace
|
||||
validates the source combination; ckprompt independent validation remains
|
||||
pending until the dependency is published and updated. Follow the
|
||||
[dependency-first release procedure](../release.md#scope-and-release-order):
|
||||
|
||||
1. When publication is authorized, publish ckconfig v0.8.0 from its independently
|
||||
validated candidate.
|
||||
2. Prepare ckprompt against the actual published ckconfig v0.8.0 using `go get`
|
||||
and `go mod download` with `GOWORK=off GOTOOLCHAIN=local`, retaining the real
|
||||
checksums. Complete its v0.8.0 release note, compatibility guidance, and
|
||||
candidate preparation under the existing rules for its other dependencies.
|
||||
3. Independently validate and publish ckprompt v0.8.0 under the same
|
||||
authorization and procedure. Track hosted release delivery separately under
|
||||
the runbook.
|
||||
|
||||
## Optional verification
|
||||
|
||||
### Optional shell completion validation
|
||||
|
||||
Reference in New Issue
Block a user