Upload missing Gitea release assets
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
# ReleaseKit staged implementation plan
|
||||
|
||||
Status: In progress. Stages 1–13 are complete; later stages remain pending.
|
||||
Status: In progress. Stages 1–14 are complete; later stages remain pending.
|
||||
|
||||
Date: 2026-10-05
|
||||
|
||||
@@ -775,7 +775,7 @@ by inspection tests.
|
||||
|
||||
## Stage 14: Upload missing assets and report partial delivery
|
||||
|
||||
Status: Pending. Depends on Stage 13.
|
||||
Status: Complete. Depends on Stage 13.
|
||||
|
||||
1. Add multipart uploads for missing binaries in filename order, followed by a
|
||||
missing manifest. Record completed work and pending asset identities.
|
||||
|
||||
@@ -2,9 +2,9 @@
|
||||
|
||||
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; the internal Gitea page and asset-inspection
|
||||
client is implemented, while asset delivery, facade/CLI integration, and
|
||||
broader integrations remain planned. The public facade architecture is
|
||||
current implemented boundary; the internal Gitea page and asset-delivery
|
||||
client is implemented, while 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.
|
||||
The [implementation plan](implementation.md) owns ordered stages, execution
|
||||
@@ -56,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. The internal
|
||||
Gitea page and asset-inspection client is implemented; delivery orchestration
|
||||
remains planned. The separate public `buildinfo` package provides lightweight
|
||||
validation, source publication, and selected-target builds. Internal Gitea
|
||||
page and asset-delivery operations are implemented; facade and CLI orchestration
|
||||
remain planned. The separate public `buildinfo` package provides lightweight
|
||||
runtime version access.
|
||||
|
||||
Each facade owns its public named types and documented contracts. Public
|
||||
|
||||
Reference in New Issue
Block a user