Verify tag-selected tool versions
This commit is contained in:
@@ -547,6 +547,15 @@ and propagation of its exit status. Existing delivery tests own hosted behavior.
|
||||
|
||||
## Stage 13: Verify upgrades, retries, and bootstrap variants
|
||||
|
||||
**Completion:** Complete. The tag workflow is exercised against a local module
|
||||
proxy with two tool versions, an older tagged configuration after the default
|
||||
branch upgrades, and a versioned replacement. Missing tool-only dependency
|
||||
checksums are prepared in temporary module metadata. The ReleaseKit source
|
||||
workflow verifies its tag before self-bootstrap and writes the executable
|
||||
outside the checkout. Delivery, configuration, and CLI guidance now distinguish
|
||||
tool bootstrap from application dependency preparation and describe
|
||||
immutable-source retries and installed-tool use.
|
||||
|
||||
**Outcome:** Tool selection follows the triggering release across supported uses.
|
||||
|
||||
1. Extend Stage 12's bootstrap fixtures with a local module proxy for two tool
|
||||
|
||||
Reference in New Issue
Block a user