CI/CD
Rollbacks
Rollback lives on the app Deployment tab: Instant Rollback, Rollback Config, Redeploy, and Promote. Instant Rollback re-deploys a stored image tag. Rollback Config restores a previous app spec.
There is no CLI rollback command. Use the dashboard, or call the deployments API with Authorization: Bearer $STACKBLAZE_TOKEN.
Database migrations are not rolled back
Rolling back your application code or spec does not undo database schema changes. If the new deployment ran migrations, handle that separately. Design migrations to be backward-compatible (additive-only) so the previous code version can run against the new schema safely.
Deployment history
feat: add rate limiting
2 hours ago
fix: resolve auth bug
5 hours ago
feat: user dashboard v2
1 day ago
chore: update deps
2 days ago
Deployments API
# Image rollback — Instant Rollback
curl -X PUT "https://api.stackblaze.cloud/api/deployments/{pipeline}/{phase}/{app}/{tag}" \
-H "Authorization: Bearer $STACKBLAZE_TOKEN"
# Preview a config rollback (read-only)
curl "https://api.stackblaze.cloud/api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId}" \
-H "Authorization: Bearer $STACKBLAZE_TOKEN"
# Apply a config/spec rollback
curl -X POST "https://api.stackblaze.cloud/api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId}" \
-H "Authorization: Bearer $STACKBLAZE_TOKEN"
Under the hood
- Instant Rollback:
PUT /api/deployments/{pipeline}/{phase}/{app}/{tag}rolls the app onto that stored image. No rebuild. - Rollback Config:
POST /api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId}applies a previous spec as a new save. Add-ons, volumes, and domains stay live. - Preview first:
GET /api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId}is read-only. The dashboard uses it for the review-changes modal.
Step by step
Open the Deployment tab
From the app, open the Deployment tab (also listed as Build history and rollbacks). You see builds and config revisions — Instant Rollback, Rollback Config, Redeploy, and Promote.
Instant Rollback (image)
Pick a previous image tag and confirm Instant rollback? That reuses the stored image — no rebuild. Same action as PUT /api/deployments/{pipeline}/{phase}/{app}/{tag}.
Rollback Config (spec)
Use Rollback Config when the bad change was settings, not the image. GET /api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId} previews the current spec and the spec that would be applied. POST /api/deployments/rollback/{pipeline}/{phase}/{app}/{revisionId} applies that config rollback.
Confirm, then watch the rollout
Confirm in the rollback review modal. Restart is not a rollback. Follow the Deployment tab until the rolled-back revision is live.