Rollbacks let you quickly revert to a previous version when something goes wrong. Turtleship keeps the build history of every hosted environment, so you can put an earlier version back live with a couple of clicks.

When to Rollback

Critical bugs discovered in production
Performance degradation
Any unexpected behavior affecting users

✨Don't Hesitate

If something looks wrong after a deploy, roll back first, investigate later. A quick rollback minimizes user impact.

How to Rollback

Open your environment

Go to Project Settings → Hosting & deployment and expand Manage environment for the environment you want to revert (staging or production).

Open the version history

Click Version history. You'll see the most recent builds with their commit, status and time.

Roll back

Click Roll back on the last known good build and confirm. Turtleship pins your app to that version and redeploys it.

Confirmation

The rollback is tracked like any other deploy: Turtleship verifies with the hosting platform that the chosen version is actually running before it reports success. You get a notification either way.

What Happens During Rollback

Your app is pinned to the chosen version (commit)
A new deploy of exactly that version is built and started
Turtleship confirms the version is live and healthy

⚠️Data Considerations

Rollbacks restore code only, not database changes. If your deployment included database migrations, those may need separate attention — ask in the project chat if you're unsure.

💡Moving forward again

A rollback pins your app to one specific version: new merges won't go live until you deploy again. Use Redeploy (or the next regular release) to move back to the latest version.

Best Practices

Test thoroughly on staging before approving a release
Keep releases small for easier rollbacks
Check the app right after a deploy — the live badge shows its real status