CLI reference / release / catalog / pin-input

stado release catalog pin-input

Invocation

stado release catalog pin-input [OPTIONS] --name <NAME> --source <SOURCE> --revision <REVISION> <CHECKOUT>

Purpose

Make one committed revision of another repository, or only the paths of it the build reads (--path, repeatable), an immutable build input of the product in CHECKOUT: archive it, store it create-only under the product's sources, and write `inputs.<name>` of its `.wisent-release.json`. The build reads it from WISENT_INPUT_<NAME>_DIR. --cargo publishes Cargo.lock's private crates, --git-bundle the commit's history, --swiftpm a Swift package's committed resolution

Required inputs and options

Input or optionContract
<CHECKOUT>The product checkout whose release manifest gains the input
--name <NAME>Input name, mount and environment key
--source <SOURCE>The repository whose committed source is published
--revision <REVISION>Commit, tag or branch to pin
--path <PATHS>Keep these repository paths; repeat for several
--cargoExport Cargo.lock's private Git crates instead of the repository tree. Requires --name private-cargo-sources and committed Cargo manifests
--git-bundleExport the pinned commit and its reachable history as a Git bundle. Use with stado web quality/build --git-input NAME=OWNER/REPOSITORY.git
--swiftpmResolve the Swift package in --source as its committed Package.resolved pins it and publish that resolution (`.build/` checkouts, repositories, artifacts and workspace state) as an archive the release script unpacks into the source before building offline. Package.swift and Package.resolved must be committed unchanged
--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

  • Requires --name private-cargo-sources and committed Cargo manifests
  • Package.swift and Package.resolved must be committed unchanged
  • 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.