Caddi
Sign inSign up

Revert

When something on production goes wrong, you want to undo — not patch. Revert opens an inverse PR that takes the branch back to the previous green SHA.

One-click revert

From the project page, click Revert on any environment. Caddi:

  • Looks up the previous successful deploy SHA.
  • Opens a PR from a temporary branch that reverts only the last promotion commit.
  • Auto-merges the PR (revert PRs skip the approval gate).
  • Watches the resulting deploy.

From the CLI

bash
caddi revert production

# previous good sha:  a1f7b9c  (deploy #2017)
# current head:       4d29ee3  (deploy #2018, failing)
# opening PR to revert 4d29ee3
# merged
# deploy queued       #2019
# ready               https://meridian.studio

Reverting an older deploy

bash
caddi promotions list --env production

# #2018  a1f7b9c → 4d29ee3   ✗ failed
# #2017  e9d2244 → a1f7b9c   ✓ ok
# #2016  c0b2210 → e9d2244   ✓ ok

caddi revert production --to e9d2244

Pass --to <sha> to roll back to a specific historical SHA instead of the immediate previous one.

Reverts write an audit log entry tagged deploy.reverted with the from-SHA and to-SHA. They’re always recoverable — your branch history is preserved, and you can “re-apply” the reverted change later via another PR.

If the rolled-back deploy depends on a migration

Caddi doesn’t know about your database. A revert restores the previous code, not previous data. If a release ran an irreversible migration, revert the code first to stop the bleeding, then handle the data manually.

Next

Env vars →