workflow.release.default¶
Release a set of packages: the branch decides the act.
Names the set positionally (packages/forge or just forge).
On a main-family branch this is the release train: one PR,
receipts per member, re-running the recovery at every step;
--armed follows the pull request to its squash and the wave
to its verdict, from main, the way submit --armed follows a
feature pull request, and an unarmed run returns at once. On
any other branch it is the dev act: a wheel straight from the
branch at a dev version, published only to the configured custom
index after a confirmation, no reserved branch, no PR, no tags.
--local is everything that stays on this machine, on either
branch mode. --workshop applies only to the recovery of a
died wave: the named release drives the wave in place of the
squash's own workshop. --abandon gives up that recovery: when
no released workshop can drive the died wave, a new release of
the set takes its uncut receipts over.
fm workflow.release.default [<paths> ...] [--armed] [--local] [--force-unverified-base] [--workshop=VALUE] [--abandon]
| Parameter | Type | Default | Description |
|---|---|---|---|
<paths>... |
variadic | ||
--armed |
flag | false |
arm the release PR to merge on green |
--local |
flag | false |
derive, build, validate, report; nothing leaves the machine |
--force-unverified-base |
flag | false |
release without waiting for the base's own CI |
--workshop=VALUE |
"" |
a released livery-workshop version to drive a re-dispatched wave | |
--abandon |
flag | false |
prepare a new release over a died wave of this set instead of re-dispatching it |