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

Upgrade the release tooling to ReleaseKit v0.3.0

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-09 03:48:52 +00:00
parent dc0adf5751
commit 03c44923c8
5 changed files with 27 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/release.md
View File

@@ -74,7 +74,7 @@ For an optional local diagnostic of a committed candidate, run:
```
This is not a required step before publication. The upstream
[candidate-check contract](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.2.0/docs/consumers/check.md)
[candidate-check contract](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.3.0/docs/consumers/check.md)
describes its requirements.
Run the single publication command with the chosen version:
@@ -114,7 +114,7 @@ resolved. ReleaseKit reports the attempted version, tag object, and recovery
state, including the captured publication endpoint when available. Use that
endpoint—not merely the current `origin` URL—to query the exact tag; follow the
upstream
[failure-recovery procedure](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.2.0/docs/release.md#resolve-failures):
[failure-recovery procedure](https://gitea.maximumdirect.net/eric/ReleaseKit/src/tag/v0.3.0/docs/release.md#resolve-failures):
```sh
releasekit_endpoint='COPY_CAPTURED_ENDPOINT'

15
docs/roadmap/releasekit.md
View File

@@ -1,6 +1,8 @@
# ReleaseKit v0.3.0 Upgrade Roadmap
Status: Accepted; implementation pending.
Status: Complete. ReleaseKit v0.3.0 is selected and the upgraded integration
is verified. Current workflow requirements belong in the
[release procedure](../release.md) and [release policy](../policy/release.md).
## Purpose
@@ -12,7 +14,7 @@ wrappers, and product-specific checks locally.
This is a focused tooling upgrade, not another release-process migration.
The [release policy](../policy/release.md) and
[release procedure](../release.md) continue to own PromptKit's release
requirements and workflow. A separate implementation plan will own staged work.
requirements and workflow. The upgrade was implemented as one focused unit.
## Current Baseline And Reviewed Upstream
@@ -111,3 +113,12 @@ Completion means v0.3.0 is selected, wiring verification passes without a
duplicated version pin, and current documentation agrees with the adopted
tool. No real tag publication is part of implementation verification. Future
PromptKit release preparation remains a separate task under the runbook.
Implementation verification passed with Go 1.26.8: the module-selected wrapper
reported `releasekit v0.3.0`, the disposable publication and failure fixtures
passed, and the ordinary offline Go suite, full vet, and maintained consumer
examples passed. The fixtures also verified native usage status, same-Go
bootstrap, and unchanged candidate module metadata. Release profile and wrapper
contents are unchanged; no real PromptKit tag was published. Upstream notices
were reviewed; the tooling-only upgrade introduced no incorporated material
requiring a new attribution entry.