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, 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. Stado Desktop shows the same register and the same failure text on its Releases screen.

Required inputs and options

Input or optionContract
[PRODUCT]Positional input; required or optional as shown in the invocation.
--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

  • 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.