CLI reference / release

stado release

Invocation

stado release <COMMAND>

Purpose

Build once, sign, promote, roll out, and roll back product releases

Required inputs and options

This command has no command-specific inputs or options.

Output and state effect

This command group selects one of the subcommands listed below; use its exact child invocation to perform an operation.

Refusals

• Before dispatch, Stado refuses a missing required token shown in the invocation, an unknown option, or a value outside a listed value set; argument-usage failures exit with code 2.

Subcommands

• keygen — Generate an Ed25519 release authority key pair
• policy — Apply, read and remove the reviewed rollout policy of each release-controlled product
• submit — Snapshot, qualify, build, sign, publish, deliver, and promote a product
• newest — Release every product in this workspace from the commit and version it already declares
• changes — Hand pushed work to a later batch release, without starting a build
• resume — Resume a recorded release without replacing its source or running jobs
• redeliver — Re-run one delivery from an exact completed release without promotion
• catalog — Manage the Stado-owned product and source policy catalog
• destinations — Manage product delivery destinations in the canonical registry
• delivery — The target-side half of one delivery, run by the queue job the release's delivery step submits
• prepare — Build, sign, and publish one immutable candidate coordinate
• fetch — Fetch signed, qualified archive bytes for one exact accepted source revision
• promote — Promote exact qualified candidate bytes into registry desired state
• agent — Run one reconcile pass of desired releases on this exact registry target (`--once`); the resident reconciler is the `--release-interval-seconds` role of `stado serve`
• status — Show desired and observed rollout state, and the register of recent publication attempts
• failed — Every Stado release a host of the fleet recorded as failed and rolled back from, as the hosts' health beacons publish them
• active — The release this host runs for a product: its executable, or a path under its release directory
• logs — Read a release candidate's own stdout/stderr off the target host
• doctor — One verdict over desired state, the candidate, quarantine and the host's claiming gates
• quarantine — List and retire the digests a host refuses to roll out again
• rollback — Atomically restore the previous desired release
• local — A release archive on this very host: install a delivered one, restore one an earlier delivery retained, list the retained ones, or converge the live readers of an already-installed binary
• coordinate — An immutable release coordinate: claim it for exactly one source revision before anything is published into it
• version — A host's declared managed binary version: declare, unset or promote it, show it against what the host runs, or converge the host onto it
• staged — A host's already-staged release
• provenance — Attest the source and bytes of the release artifacts a host carries
• gate — The pull-request version gate's steps: the advertised surface, the published baseline, the versioning rule and the module reachability check `.github/workflows/version-check.yml` runs