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

Prepare the initial v0.1.0 release

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-07 02:49:47 +00:00
parent dab4fdf2b3
commit 5e60fe3113
10 changed files with 89 additions and 1198 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/roadmap/releasekit.md
View File

@@ -1,7 +1,7 @@
# ReleaseKit: shared release process
Status: Initial implementation, policy adoption, and architecture remediation
are complete. Consumer adoption, publication, and live integration work remain.
are complete. Consumer adoption and live CI integration work remain.
This roadmap records the shared release-process opportunity identified in
PromptKit, ConfigKit, Audita, Notarius, Narratio, and Scriptorium on 2026-09-29,
@@ -227,20 +227,23 @@ publication and delivery operations.
## Remaining work
- Prepare and publish the first ReleaseKit source release under the
[maintainer procedure](../release.md), then deliver its hosted note page.
- Use the [v0.1.0 baseline](../releases/v0.1.0.md) for initial consumer integration
under the [maintainer procedure](../release.md).
- Choose the broader consumer integration test plan and migration sequence.
Evaluate API clarity, product-specific checks, and the infrastructure removed
from each consuming repository.
- Replace the maintained example's ReleaseKit version placeholder with a real
immutable revision or published version. Provision delivery credentials and
activate consumer Woodpecker workflows as part of deployment.
- Provision delivery credentials and activate consumer Woodpecker workflows
using the maintained example's `v0.1.0` pin or a later selected immutable
version as part of deployment.
- Verify live Gitea delivery and Woodpecker execution. Existing verification uses
local Git and HTTP fixtures; no live deployment has been verified.
- Keep ReleaseKit executable binary distribution deferred until deliverables
are deliberately selected. Selecting binaries would require delivery
declarations, target checks, automation responsibilities, and corresponding
release policy and procedure updates.
- Evaluate a maintained ReleaseKit CI image or specialized validation/build
settings when a demonstrated consumer need justifies their maintenance cost
under [ADR 0002](../adr/0002-routine-releases.md).
## Reviewed implementations