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

Consolidate Woodpecker delivery templates

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-06 19:49:19 +00:00
parent c6a5db8aeb
commit 21294404d7
12 changed files with 295 additions and 184 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
docs/roadmap/audit.md
View File

@@ -227,11 +227,12 @@ when needed.
### F6 — Adoption priority: shared deployment still depends on copied mechanics
**Evidence.** The [source-only](../../examples/woodpecker/tag-delivery-source-only.yml)
and [binary](../../examples/woodpecker/tag-delivery-binary.yml) templates repeat
fetch/checkout guards, local exclusions, cache setup, and tool installation.
The binary template adds an explicit build/receipt/deliver sequence even though
the CLI already supports combined delivery. ReleaseKit's
**Evidence.** The original source-only and binary templates repeated
fetch/checkout guards, local exclusions, cache setup, and tool installation;
they are now consolidated in the maintained
[tag-delivery template](../../examples/woodpecker/tag-delivery.yml). The binary
template added an explicit build/receipt/deliver sequence even though the CLI
already supports combined delivery. ReleaseKit's
[own workflow](../../examples/woodpecker/releasekit-source-delivery.yml) has a
separate first-release bootstrap. Consumer pins remain placeholders as documented.
@@ -249,14 +250,14 @@ Keep dependency preparation separate from offline validation/builds. A split
build/delivery flow remains useful for an actual credential boundary or artifact
handoff. See Design Choice 4 for packaging alternatives.
`TestWoodpeckerDeliveryCommandSequences` in
[the CLI workflow tests](../../cmd/releasekit/woodpecker_test.go) executes
equivalent commands;
[the ReleaseKit workflow test](../../cmd/releasekit/releasekit_delivery_workflow_test.go)
similarly reconstructs the sequence. Execution of the maintained YAML and
installation step remains unverified. A YAML drift can leave these tests green.
Validate the selected integration during adoption and keep a small check tied to
the maintained artifact. Use that evidence to maintain the shared integration.
The original `TestWoodpeckerDeliveryCommandSequences` and the ReleaseKit
workflow test reconstructed workflow commands, so YAML drift could leave the
tests green. The maintained tag template and ReleaseKit's bootstrap workflow
are now exercised from their command blocks by local Git/HTTP fixtures. The Go
bootstrap shim verifies template arguments while mapping the pinned module
invocation to the test executable; it does not verify published-module
availability. Real installation and live Woodpecker execution remain
deployment work.
### F7 — Medium: delivery asset classifications overlap inconsistently