delimit_release_rollback
Revert a whole environment to a prior release version when services show regressions, ensuring coordinated rollback across apps.
Instructions
Revert a whole environment to a prior release version (experimental).
When to use: when delimit_release_validate or delimit_obs_alerts indicate a regression that spans services and you need to revert the WHOLE environment to a known-good release, not just one app. Typical sequence: alert fires -> delimit_release_history to pick a target -> this -> delimit_release_status to confirm. When NOT to use: to roll back a single app at the SHA level (use delimit_deploy_rollback), to roll back an npm publish (npm publish history is largely append-only — there is no clean rollback), or to roll forward (delimit_release_plan).
Sibling contrast: delimit_deploy_rollback reverts one app at
the SHA level; this reverts a release version across services
in lockstep. delimit_release_history is how you pick the
to_version.
Side effects: invokes backends.ops_bridge.release_rollback which
MUTATES the live environment — services are flipped to the
to_version artifacts. No license gate at this level (handled
by the backend's own admin checks). Marked EXPERIMENTAL —
handler may return partial results on backends without rollback
automation; verify with delimit_release_status afterwards. No
automatic ledger write, no automatic notification — pair with
delimit_evidence_collect + delimit_notify per the deploy-gate
chain.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| environment | Yes | Target environment. Required. | |
| version | Yes | Current release version that is failing. Required. | |
| to_version | Yes | Prior release version to roll back to. Required. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||