Rollback

Every deploy freezes what it shipped: the exact image per service and the spec it ran with. Rolling back re-ships that frozen state. Nothing is rebuilt and nothing is re-read from your repository.

​

Rolling back

Open the project’s History tab. A superseded deploy carries a rollback action. Confirming it creates a new deployment with trigger rollback that goes straight to the deploy phase using the old images. Because nothing builds, a rollback takes about as long as pods take to start.

​

What rollback does exactly

Because the next push supersedes it, use rollback to recover. To stay on a known commit, turn auto-deploy off for that source.

​

When rollback is refused

Old images do not live forever. The registry keeps each service’s last few builds plus everything a live deploy still references. If cleanup has reclaimed an image, the rollback is refused and names the reason. Redeploy the commit instead, which rebuilds it. Deployments made before image manifests existed also cannot roll back, and redeploy instead.