Invoke the registered ReleaseKit package explicitly
This commit is contained in:
11
docs/cli.md
11
docs/cli.md
@@ -342,11 +342,12 @@ status 2. Final delivery uses the same statuses as `deliver`: 0 for complete,
|
||||
state, including when cancellation prevents reconciliation.
|
||||
|
||||
The maintained module-based tag workflow verifies and checks out the event tag
|
||||
before resolving the consumer module. It runs `go tool releasekit` for the version
|
||||
already selected by that tagged `go.mod`, using temporary alternate module files
|
||||
outside the source checkout. This tool bootstrap is separate from `ci-deliver`'s
|
||||
application dependency preparation for binary profiles. ReleaseKit's own
|
||||
source workflow self-bootstraps `./cmd/releasekit`; consumers without a declared
|
||||
before resolving the consumer module. It invokes the ReleaseKit tool by its full
|
||||
package path for the version already selected by that tagged `go.mod`, using
|
||||
temporary alternate module files outside the source checkout. This tool bootstrap
|
||||
is separate from `ci-deliver`'s application dependency preparation for binary
|
||||
profiles. ReleaseKit's own source workflow self-bootstraps `./cmd/releasekit`;
|
||||
consumers without a declared
|
||||
ReleaseKit module dependency can use the separately installed-tool command.
|
||||
See the [delivery guide](consumers/delivery.md#woodpecker-tag-workflows) for
|
||||
compatible Go environments, retries, and preparation details.
|
||||
|
||||
Reference in New Issue
Block a user