Record ckconfig source release
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# CommandKit vanity migration and dependency alignment plan
|
||||
|
||||
Status: Stages 1–3 complete; Stages 4–7 are not started.
|
||||
Status: Stages 1–4 complete; Stages 5–7 are not started.
|
||||
|
||||
This plan is for the Luna coding agent implementing the
|
||||
[feature roadmap](integration-dependency-alignment.md). Follow the stages in
|
||||
@@ -224,7 +224,11 @@ aligned current documentation/attribution.
|
||||
|
||||
## Stage 4: Validate and publish ckconfig v0.2.0
|
||||
|
||||
**Status:** not started.
|
||||
**Completed.** `go.maximumdirect.net/ckconfig v0.2.0` was published as
|
||||
`integrations/ckconfig/v0.2.0` at candidate
|
||||
`92a327db9752e7a898d14f56e86fbdee027b3126`. The ordinary Go 1.26.8 release
|
||||
workflow passed the independent suite, maintained example, and selected file
|
||||
checks before the successful source-tag push.
|
||||
|
||||
Review and commit the complete ckconfig candidate. From the repository root,
|
||||
use the same authoritative-branch protocol as Stage 2:
|
||||
|
||||
Reference in New Issue
Block a user