Expose tagged-source delivery through facade and CLI
This commit is contained in:
@@ -26,13 +26,15 @@ Implemented internal packages:
|
||||
creates and pushes exact annotated tag objects.
|
||||
- `internal/publish` coordinates local and remote guards around one validation
|
||||
run and reports the publication state reached by that invocation.
|
||||
- `internal/delivery` verifies a tagged checkout and coordinates note, build
|
||||
identity, hosted page, asset inspection, and additive upload outcomes.
|
||||
- `cmd/releasekit/internal/cli` parses implemented commands, loads strict JSON
|
||||
profiles, adapts configured checks, and writes and validates private local
|
||||
build receipts.
|
||||
build receipts used for delivery.
|
||||
|
||||
The executable controller uses the runtime facade and the command-owned CLI
|
||||
adapter. The adapter uses the process runner and imports neither public facade.
|
||||
The publication operation coordinates the candidate and Git packages. The
|
||||
internal Gitea client is documented in the
|
||||
[Gitea integration guide](../integrations/gitea.md); delivery orchestration will
|
||||
use it when that facade and CLI work lands.
|
||||
[Gitea integration guide](../integrations/gitea.md); tagged-source orchestration
|
||||
is exposed through the public delivery facade and CLI.
|
||||
|
||||
Reference in New Issue
Block a user