Adopt ConfigKit v1.2.0 in both integrations
This commit is contained in:
@@ -1,6 +1,7 @@
|
||||
# Future work
|
||||
|
||||
Status: optional shell validation and future capability proposals.
|
||||
Status: pending PromptKit adoption and integration releases, optional shell
|
||||
validation, and future capability proposals.
|
||||
No delivery dates are selected here.
|
||||
|
||||
## Purpose and authority
|
||||
@@ -30,6 +31,20 @@ 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.
|
||||
|
||||
## Pending integration work
|
||||
|
||||
ConfigKit v1.2.0 is adopted in both integration source modules. Both independent
|
||||
integration suites pass against the published dependencies, and the aligned
|
||||
workspace suites cover the current integration sources together. PromptKit is
|
||||
currently selected at v0.20.0.
|
||||
|
||||
Review and adopt the upcoming PromptKit minor release incorporating ConfigKit
|
||||
v1.2.0. Then prepare the coordinated ckconfig v0.7.0 and ckprompt v0.7.0 release
|
||||
notes and compatibility guidance with the final dependency selections. Publish
|
||||
ckconfig first, update ckprompt to that published ckconfig version, validate its
|
||||
independent candidate, and publish ckprompt. The release procedure owns version
|
||||
availability checks, final validation, and publication. [Release procedure](../release.md#scope-and-release-order).
|
||||
|
||||
## Optional verification
|
||||
|
||||
### Optional shell completion validation
|
||||
|
||||
Reference in New Issue
Block a user