GitHub release workflows

The GitHub workflows call Stado's release and host operations. Deployment coordinates belong to repository variables, not to checked-in machine names or personal home directories. These adapters do not replace the release manifest, registry or authenticated publication checks described in Release and compatibility.

Deployment inputs

Set repository variables in GitHub Settings → Secrets and variables → Actions, or through gh variable set NAME --repo wisent-ai/stado --body VALUE. Supply the actual deployment values outside source control.

Variable	Meaning
STADO_CONTROL_TARGET	Registry target of the control runner whose capacity and resolver are inspected.
STADO_OBJECT_HOST	Registry host serving the declared object API.
STADO_OBJECT_HOME	Expected HOME in the object service's declared environment.
STADO_OBJECT_CONFIG_PATH	Expected STADO_CONFIG in that service environment. This is not the runner's STADO_CONFIG_PATH.
STADO_OBJECT_VAULT_FILE	Expected SKARBIEC_VAULT_FILE in the object service environment.
STADO_OBJECT_STORAGE_PATH	Expected WC_LOCAL_STORAGE_PATH in the object service environment.
STADO_OBJECT_BACKUP_PATH	Expected WC_BACKUP_LOCAL_STORAGE_PATH in the object service environment.

deploy.yml, triggered by a stado-v* tag, requires all seven variables across its affected jobs. Its object-service checks retain the local primary and backup backend requirements of that recovery path. The five expected environment values are assertions, not settings that provision the host or relocate storage. The host's declared service configuration remains authoritative.

product-release.yml, triggered by the product-release repository dispatch event, requires STADO_CONTROL_TARGET and STADO_OBJECT_HOST. Its payload supplies the repository, exact source commit in ref, version and candidate or stable channel.

deploy-existing-release.yml requires STADO_OBJECT_HOST. Its Run workflow form accepts an existing immutable version. The equivalent CLI request is gh workflow run deploy-existing-release.yml --repo wisent-ai/stado -f version="$PRODUCT_VERSION". Recovery still uses Stado's declared object-service operation; it does not select a host by a compiled-in name.

These requirements supplement the workflows' existing Stado configuration, endpoint and credential inputs. They do not grant host access or publisher permissions.

Submit a product revision

The Submit product release Run workflow form and gh workflow run accept the same repository, revision, version and channel. The repository input is the bare repository name under wisent-ai; the revision is a full lowercase 40-character commit. The product manifest determines the version source. Select candidate or stable; preview is not a supported release-submit channel.

gh workflow run submit-product-release.yml --repo wisent-ai/stado -f repository="$PRODUCT_REPOSITORY" -f revision="$SOURCE_COMMIT" -f version="$PRODUCT_VERSION" -f channel=candidate

This adapter discovers the object service's owning host from the product catalog and service listing rather than requiring the explicit host variables above. Private source repositories require PRODUCT_SOURCE_TOKEN with read access. Checkout credentials are not persisted for publication.

Refusals and results

An unset or empty required deployment variable fails the affected job's first input step with Set the NAME repository variable. There is no personal-machine fallback. Targeted operations also use required shell expansions, including recovery and capacity steps that run after an earlier failure.

The tag workflow compares every declared environment expectation with the service report, retains token-file redaction and backend assertions, and compares the object host and control target with the directory route before a restart. A disagreement fails the step; changing a variable does not make a mismatching observed environment pass. The reports are written beneath RUNNER_TEMP, including object-api-environment.json, object-service-before-restart.json and object-dependency-before-restart.json.

A healthy process or accepted dispatch is not a completed release. The workflows retain their authenticated object reads, writes, immutable publication and final delivery checks. Read the selected Actions run's failed operation and release receipts; do not report success from variable configuration or a queued workflow alone.