Add mapped multi-module delivery workflow
This commit is contained in:
@@ -704,6 +704,18 @@ tag and verify retry still uses its original selection. Fail inconsistent mappin
|
||||
through the library's exact tag check. Isolate every synthetic dependency consumer
|
||||
with test-owned `GOMODCACHE`; use local HTTP fixtures and local Git remotes.
|
||||
|
||||
**Completed:** Added the multi-module Woodpecker workflow with full root and
|
||||
nested tag filters, exact peeled-tag commit verification, and selection from the
|
||||
verified checkout. Bootstrap uses the mapped physical module's committed Go
|
||||
metadata and profile, then invokes prepared CI delivery with the expected module,
|
||||
commit, and full tag. Added the binary core v2 example and documented committed
|
||||
module checksums for clean binary delivery. Workflow harnesses cover nested
|
||||
page-only and binary delivery, physical and virtual `/v2` module layouts, a retry
|
||||
after default-branch mapping and tool changes, and an inconsistent mapping
|
||||
rejected by exact event-tag validation. Tests use local Git remotes, local HTTP
|
||||
delivery fixtures, a local module proxy, and test-owned `GOMODCACHE`. Verified
|
||||
`go test ./...`, `go run ./internal/apicheck`, shell syntax, and `git diff --check`.
|
||||
|
||||
## Stage 15: Complete consumer documentation and verify the whole cutover
|
||||
|
||||
**Outcome:** The supported interface, examples, migration guidance, and behavioral
|
||||
|
||||
Reference in New Issue
Block a user