eric/ConfigKit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Mark ReleaseKit adoption complete

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-08 17:08:53 +00:00
parent b1ecd9a078
commit a22aaa5dfa
3 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/roadmap/implementation.md
View File

@@ -1,8 +1,9 @@
# Implement ReleaseKit adoption
Status: Planned. Implement the stages below in order. The target state and
policy choices are in the [ReleaseKit adoption roadmap](releasekit.md); this
plan is the execution checklist. Use ReleaseKit v0.2.0 at tagged commit
Status: Complete. All seven stages below have been implemented and verified.
The [ReleaseKit adoption roadmap](releasekit.md) owns the target state and
policy choices; this plan records the execution checklist. Use ReleaseKit v0.2.0
at tagged commit
`e030794969fb7787e647a90bbc4eb81bd0610f07` for the initial migration.
Do not publish a real ConfigKit version as part of implementation. Keep the
current release procedure authoritative until the replacement is working.

15
docs/roadmap/releasekit.md
View File

@@ -1,7 +1,7 @@
# Adopt ReleaseKit for source releases
Status: In progress. The ReleaseKit profile and workflow are in place; isolated
fixture verification remains in the implementation plan. This roadmap uses
Status: Complete. The ReleaseKit profile, workflow, and isolated fixture
verification are in place. This roadmap uses
ReleaseKit v0.2.0 (tagged commit
`e030794969fb7787e647a90bbc4eb81bd0610f07`) as the initial adoption
baseline. The [ReleaseKit release note](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.2.0/docs/releases/v0.2.0.md)
@@ -104,11 +104,12 @@ release process adds no ConfigKit public API or runtime use of ReleaseKit.
- Retired the local release scripts and duplicated publication/gate tests.
The development-check test and small profile-wiring test remain; generic
ReleaseKit publication behavior is not duplicated in ConfigKit's tests.
- The remaining migration verification exercises the selected profile and
release command against isolated candidates and a temporary Git remote,
including validation failure and successful tag publication. It confirms
the selected Go minimum and one invocation of each selected gate, without
publishing a real ConfigKit version or requiring a separate CI run.
- Completed migration verification exercised the selected profile and release
command against isolated candidates and a temporary Git remote, including
validation failure, successful tag publication, and wrong-endpoint rejection
before validation. It confirmed the selected Go minimum and one invocation
of each selected gate, without publishing a real ConfigKit version or
requiring a separate CI run.
Historical tags and release notes remain unchanged. This adoption work does
not itself authorize publication of a ConfigKit version.

4
docs/roadmap/remediation.md
View File

@@ -63,6 +63,10 @@ specifically for `go run`. No additional execution mode or test matrix is needed
## 3. Reconcile completed implementation status (P3)
Status: Complete. The roadmap and implementation plan now identify the migration
as complete, and the roadmap describes fixture verification as completed.
Completed documents remain available for retirement during release preparation.
Affected: the adoption roadmap's opening status and final migration-verification
bullet, and the implementation plan's opening status.