Expose tagged-source delivery through facade and CLI
This commit is contained in:
@@ -1,9 +1,11 @@
|
||||
# Gitea release pages
|
||||
|
||||
ReleaseKit's internal Gitea client verifies a hosted source tag, finds or
|
||||
creates its stable release page, inspects existing assets, and uploads missing
|
||||
assets. The public delivery facade and CLI workflow are planned separately;
|
||||
this guide describes the implemented internal operations.
|
||||
ReleaseKit's public `Deliver` operation and `deliver` command verify tagged
|
||||
source, find or create its stable release page, inspect existing assets, and
|
||||
upload missing assets through the internal Gitea client. Page-only and
|
||||
binary-producing profiles use the same delivery path. The
|
||||
[consumer delivery guide](../consumers/delivery.md) covers caller workflows;
|
||||
this guide describes the Gitea protocol and its failure behavior.
|
||||
|
||||
The caller supplies the Gitea base URL, owner, repository name, and token
|
||||
explicitly. The client does not read ambient credentials. The token is sent in
|
||||
|
||||
Reference in New Issue
Block a user