CLI reference / release / status

stado release status

Invocation

stado release status [OPTIONS] [PRODUCT]

Purpose

Show desired and observed rollout state, and the register of recent publication attempts. The newest pipeline runs are listed with each platform's job, its state, what the build cost from the job's own clock, and the recorded failure of anything that died - the builder that refused the work, the secret that could not be resolved, or the job's own last output - so a failed publication can be read back without opening the store, and a release that is getting slower can be seen without one. Stado Desktop shows the same register, the same durations and the same failure text on its Releases screen. An unfinished platform whose job is absent from every queue state is reported as failed, with its job id and the missing-job finding. Failure of a required platform also makes the observed run failed; recorded_state retains the stored run state. A queue-read failure is reported separately as job_read_error, not treated as a missing job. These are observations: status does not resubmit work or change the stored release state.

Required inputs and options

Input or optionContract
[PRODUCT]Positional input; required or optional as shown in the invocation.
--run <RUN>One pipeline run, by its id or the first characters of it as this command prints them; the target rows are left out, because the question is about the run. Found however far back it is
--version <VERSION>Only runs that published this version; with --run, both must hold
--limit <LIMIT>List only the newest N release runs; without it every recorded run is listed. Zero is refused: omit the flag to list every run
--jsonCommand option; required or optional as shown in the invocation.

Output and state effect

This is an inspection/reporting operation. It emits the result described above and does not change managed state unless an explicit option in this page says otherwise. Pass `--json` when the command exposes that machine-readable option.

Refusals

  • Only runs that published this version; with --run, both must hold
  • Zero is refused: omit the flag to list every run
  • 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.