base-layer/releasekit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Add Gitea read operations to the forge boundary

Browse Source
This commit is contained in:
Eric Rakestraw
2026-11-01 17:57:57 +00:00
parent 61a07bc950
commit 201af83d95
4 changed files with 332 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/roadmap/implementation.md
View File

@@ -1,6 +1,6 @@
# Implementation plan: neutral forge delivery and credential preflight
Status: implementation in progress; Stages 1–2 are complete and Stages 3–10
Status: implementation in progress; Stages 1–3 are complete and Stages 4–10
are pending.
## Purpose and execution
@@ -266,7 +266,7 @@ adding a guarantee against concurrent file replacement.
## Stage 3: Extract Gitea read operations
Status: pending.
Status: complete.
1. Adapt the Gitea client into a backend configured with its private destination
and optional HTTP client. Implement `TagCommit`, `FindRelease`, `ListAssets`,