CLI reference / release / newest

stado release newest

Invocation

stado release newest [OPTIONS]

Purpose

Release every product in this workspace from the commit and version it already declares. One command for the whole workspace: each product checkout is read for the commit it stands on and the version that commit declares. A version a run published is skipped, a version a run of another commit holds is skipped with the new version it needs, and a commit a run is still releasing is skipped; a commit whose own run failed or was superseded is released again. The rest go through the same pipeline `submit` drives. `--plan` reads without submitting.

Required inputs and options

Input or optionContract
--root <ROOT>The directory holding the product checkouts. Defaults to the parent of the checkout this command is run in, which is where a workspace keeps one checkout per repository
--product <PRODUCTS>Release only these products; repeat for several. The default is every product the workspace holds
--first <FIRST>Deliver these products first, in the order given; repeat the flag or separate names with commas. The rest follow in name order. Each must be a product of the plan
--channel <CHANNEL>[default: candidate] [possible values: candidate, stable]
--planRead what would be released and why the rest is skipped, without submitting anything
--registerPrint the delivery queue's register as it stands — every commit the queue kept, its state and step, the defects it carried and recorded, and when its release was published and recorded — reading no checkout and running no step; the other flags but --json are not read
--pushAfter the `--first` products are delivered and installed on this host, push every checkout of the workspace holding commits its upstream does not, read each pushed product's CI, and only then deliver the rest; unpushed commits are counted per checkout before and after. Needs `--first`: the products every push needs first
--jsonCommand option; required or optional as shown in the invocation.

Output and state effect

It performs the operation described above and emits its operator result on standard output or standard error. Any state change is limited to the resources and records named by the purpose and options on this page.

Refusals

  • Each must be a product of the plan
  • 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.