9 Command-Line Workflow
The command inventory below mirrors "rivet-cli/usage.rkt", which is the single source of truth for every flag and variant; run raco rivet help for the full annotated table.
raco rivet new <name> [--with-updates] create a native starter project |
raco rivet doctor [--json] [--release] inspect the native toolchain; the |
--release form runs the release gate |
raco rivet entitlements --json|--plist|--check APP |
emit or enforce macOS entitlements |
raco rivet inspect [--json] show the project edit/verification map |
raco rivet acceptance [--json] [--dry-run] [--suite <id>] |
run declared acceptance suites |
raco rivet matrix <report.json>... aggregate per-platform acceptance reports |
raco rivet verify-remote --repo O/R --ref REF |
trigger and fold remote acceptance legs |
raco rivet schema --json|--output <file>|check <file> |
emit, baseline, or reject API changes |
raco rivet clean remove generated .rivet/build/dist output |
raco rivet support-bundle collect a redacted doctor/inspect/log bundle |
raco rivet build compile backend and native host |
raco rivet generate [--check] regenerate Swift, C++, and Kotlin clients |
raco rivet dev build and run the current application |
raco rivet package [--production] create and verify a distributable |
raco rivet release [--development] [--without-updates] [--update-payload ...] |
build installer, signed update manifest, SBOM |
raco rivet manifest-compose <inputs...> compose update manifests |
raco rivet sign-manifest ... compose and sign a family update manifest |
raco rivet verify-release-assets ... verify signed release asset parity |
raco rivet i18n verify shared/i18n parity, regenerate tables |
raco rivet measure size|startup report artifact size/launch against budgets |
raco rivet compliance generate SBOM/notices and run the license audit |
raco rivet apple-review --channel ... inspect an actual Apple artifact |
raco rivet verify [--production] re-verify the current packaged artifact |
raco rivet help; raco rivet --version help text; installed release version |
Production application releases require publisher-controlled platform signing credentials and a separate Ed25519 update-signing key. Secrets must be supplied through the documented release environment and must not be committed to an application or to Rivet.