Rollbacks

Every deployment produces an immutable container image that is retained in your cloud provider’s registry. Rolling back reactivates a previous image — no rebuild required.

Rolling back

ske rollback

⠋ Rolling back to deployment #41...
✓ Rollback succeeded (45s)

By default, ske rollback reverts to the most recent successful deployment before the current one.

Rolling back to a specific version

Use --to to target a specific deployment:

ske rollback --to 38

⠋ Rolling back to deployment #38...
✓ Rollback succeeded (42s)

Find the deployment ID with ske deploy list:

ske deploy list

  ID    TYPE        STATUS      INITIATOR          CREATED
  42    deploy      succeeded   you@example.com    2026-09-20 14:30
  41    deploy      succeeded   you@example.com    2026-09-19 09:15
  40    rollback    succeeded   you@example.com    2026-09-18 16:00
  39    deploy      succeeded   ci@example.com     2026-09-17 12:00
  38    deploy      succeeded   ci@example.com     2026-09-16 14:00

How rollbacks work

A rollback creates a new deployment record of type rollback. It does not delete the deployment you’re rolling back from — that image remains available for future use.

The rollback process:

1. Locates the target deployment’s container image in your registry
2. Updates the compute configuration (Lambda function or Cloud Run service) to use that image
3. Routes traffic to the rolled-back version

Because the image already exists in your registry, rollbacks take under a minute instead of the full build-push-provision cycle.

What rollbacks don’t revert

Rollbacks revert the application code. They do not revert:

• Secrets — secret values are applied at container startup from your cloud provider’s secret store. A rollback uses the current secrets, not the ones that were set at the time of the original deployment.
• Infrastructure — databases, caches, networks, and their configurations are not affected.
• Database migrations — if the deployment you’re rolling back from ran migrations, those changes remain. Make sure your migrations are backward-compatible.

Rollbacks in CI

# Roll back production to deployment 38
ske rollback --to 38 --env production --json

The --json flag outputs machine-readable JSON for pipeline integrations.