stado release gate
Invocation
stado release gate <COMMAND>Purpose
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
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
surface— Print `{"surface": [...]}`: the top-level commands BINARY advertises in `help`, or those in a saved help textbaseline— Print `stado:VERSION` for the newest whole release the channel serves, or `bootstrap:VERSION` on an empty one; with --output, also write the baseline document. Run from the repository rootdecide— Classify the change between two surfaces and name the next versionconformance— Reproduce every case of AutoVersion's FIXTURES.md with this port; fails when any class, next version or refusal differs. Without --fixtures, the file at the tag this port follows is readsemver— A declared version against the one the rule requiresmodules— The crate's module treeapp— The same gate for an application bundle, read from the sources its release step names