Skip to content

workflow.release.publish

Publish the squash at --ref: the wave, receipts cut per member.

The CI entry point after a release PR merges, and the recovery entry when a publish died mid-wave: everything already tagged is walked past. --ref exists because HEAD usually moves past the squash before a recovery runs. Each member publishes to the registry of the ecosystem its extensions release it to, and the wave reads what that registry serves through the probe they answer: the resolved index for a python package, the resolved conan target for a conan recipe that names a reference. --prebuilt says the jobs of the run already built the members they build before the wave, the workspace's job-built-members answer: a platform-wheel member's dist/ holds the wheels collected from every platform, a conan member's the caches saved on every host, and the wave publishes them instead of building on this runner alone. Inside CI the wave decides that for itself: such a member whose dist/ already holds a file was fed by the run, since a runner's checkout starts with none.

Hidden: this task is not listed by fm --list, --tree or completion — it runs like any other when named.

fm workflow.release.publish [--ref=VALUE] [--prebuilt]
Parameter Type Default Description
--ref=VALUE "" the release squash; empty means HEAD
--prebuilt flag false trust the dist/ the run collected for each member a job builds

Example

$ fm workflow.release.publish --prebuilt