Validate CI module tags before delivery preparation
This commit is contained in:
@@ -244,9 +244,11 @@ verifies the tag, HEAD, and clean worktree. With `--prepared`, it performs those
|
||||
checks read-only against the existing checkout and does not fetch or check out.
|
||||
In either mode, it loads the profile from the verified source. `--expected-module`
|
||||
optionally checks that the profile selects the module chosen by a launcher;
|
||||
module selection itself remains profile-owned. The command validates explicit
|
||||
forge selection and resolves the configured token. For binary profiles, it
|
||||
performs a read-only repository preflight before downloading application
|
||||
module selection itself remains profile-owned. The command compares the selected
|
||||
module's derived release tag with the full event tag before forge access or
|
||||
dependency preparation, then validates explicit forge selection and resolves
|
||||
the configured token. For binary profiles, it performs a read-only repository
|
||||
preflight before downloading application
|
||||
dependencies; delivery performs a fresh check after dependency preparation.
|
||||
Source-only profiles rely on delivery's automatic preflight and skip dependency
|
||||
downloads and binary builds.
|
||||
|
||||
Reference in New Issue
Block a user