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

Adopt PromptKit v0.21.0 and prepare integration release notes

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-10 15:30:59 +00:00
parent 07a329033c
commit 64f6453b84
8 changed files with 79 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

21
docs/roadmap/future.md
View File

@@ -1,6 +1,6 @@
# Future work
Status: pending PromptKit adoption and integration releases, optional shell
Status: pending integration releases, optional shell
validation, and future capability proposals.
No delivery dates are selected here.
@@ -33,17 +33,16 @@ 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.
ConfigKit v1.2.0 is adopted in both integration source modules, and ckprompt
selects PromptKit v0.21.0. Release notes for ckconfig v0.7.0 and ckprompt v0.7.0
are prepared in their respective release directories.
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).
Publish ckconfig v0.7.0 first. Then update ckprompt's declared ckconfig dependency
from v0.6.0 to the published v0.7.0, refresh its checksums, and validate its
independent candidate before publishing ckprompt v0.7.0. Update the consumer
guide's published-version table as each release becomes available. The release
procedure owns version availability checks, final validation, and publication.
[Release procedure](../release.md#scope-and-release-order).
## Optional verification