stado product deliver
Invocation
stado product deliver [OPTIONS] <COMMAND>Purpose
Release deliveries to hosting providers, run by a manifest's deliveries
Required inputs and options
| Input or option | Contract |
|---|---|
--catalog <catalog> | Independent authoritative catalog path |
--workspace <workspace> | The workspace of canonical checkouts this operation reads and builds from; default WISENT_WORKSPACE, else ~/Documents/CodingProjects/Wisent |
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
schema— Apply the verified release's migrations to the product's database on its engine. postgres: verify WISENT_RELEASE_ARCHIVE against WISENT_RELEASE_SHA256, read its one database-schema.tar, then apply the migrations the database SCHEMA_DATABASE_URL names has not recorded yet, each with its version recorded in wisent_schema_migrations; writes schema-receipt.json. supabase: push supabase-source.tar (migrations, functions) to the project SUPABASE_PROJECT_REF with SUPABASE_ACCESS_TOKEN and SUPABASE_DB_PASSWORD, carrying split migrations in as applied. Declared supabase/function-secrets.json names are resolved from injected environment values before mutations and published before functions deploy; writes supabase-receipt.json with secret names, never values. sqlite has no delivery: the product applies its own migrations on opentestflight— Upload the verified release's .ipa to App Store Connect with xcrun altool (AC_API_KEY_ID, AC_API_ISSUER_ID, AC_API_KEY_P8); writes testflight-receipt.jsongithub-mirror— Mirror the verified release on GitHub (WISENT_MIRROR_TOKEN): tag v<version> at the release's SOURCE_REVISION, a release titled '<title> <version>', and the archive as its asset; writes github-mirror-receipt.jsonnpm— Publish the verified release's npm-package.tgz unchanged (NPM_TOKEN), running no package scripts; writes npm-receipt.jsonrender— Start a deploy of the Render service of this name (RENDER_API_KEY); writes render-evidence.json with the deploy and the status Render answeredvercel-files— Upload the source/ files of a bundle in the verified release to Vercel (VERCEL_TOKEN) as a production deployment and wait until it is ready; writes vercel-evidence.json