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

Add Gitea release page transport

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-05 19:46:27 +00:00
parent e98ee0f7b9
commit 717d6d0d04
7 changed files with 756 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# ReleaseKit staged implementation plan
Status: In progress. Stages 1–11 are complete; later stages remain pending.
Status: In progress. Stages 1–12 are complete; later stages remain pending.
Date: 2026-10-05
@@ -736,7 +736,7 @@ no publication or consumer pilot is needed to complete this stage.
## Stage 12: Find and create Gitea release pages
Status: Pending. Depends on Stage 11.
Status: Complete. Depends on Stage 11.
1. Implement the small internal REST transport using the served API operations,
explicit destination/token inputs, context cancellation, and structured

9
docs/roadmap/releasekit.md
View File

@@ -2,7 +2,8 @@
This is a proposal based on a review of PromptKit, ConfigKit, Audita, Notarius,
Narratio, and Scriptorium on 2026-09-29. The implementation plan records the
current implemented boundary; delivery and broader integrations remain
current implemented boundary; the internal Gitea page client is implemented,
while asset delivery, facade/CLI integration, and broader integrations remain
planned. The public facade architecture is accepted in
[ADR 0001](../adr/0001-public-facade.md) and is implemented for runtime version,
candidate validation, and source publication.
@@ -55,9 +56,9 @@ cleanup.
The [architecture policy](../policy/architecture.md) owns the adopted
responsibility and dependency rules, including the runtime version boundary.
The root `releasekit` package provides the public facade for candidate
validation, source publication, and selected-target builds. Delivery remains
planned. The separate public `buildinfo` package provides lightweight runtime
version access.
validation, source publication, and selected-target builds. The internal
Gitea page client is implemented; delivery orchestration remains planned. The
separate public `buildinfo` package provides lightweight runtime version access.
Each facade owns its public named types and documented contracts. Public
operations, inputs, outcomes, errors, and callbacks express deliberately