Rolling Back Updates
A deployment's release history is immutable, so you cannot delete or remove individual updates once they have been released without deleting all of the deployment's release history. However, if you release an update that is broken or contains unintended features, it is easy to roll it back using the rollback command:
npx turbopush rollback <appSlug> <deploymentName>
npx turbopush rollback myapp-ios Production
How It Works
Rollback creates a new release with the exact code and metadata from the previous version.
| Release | Description | Mandatory |
|---|---|---|
| v1 | Initial release | Yes |
| v2 | New feature | No |
| v3 | Bug fixes | Yes |
| v4 (rollback) | New feature | No |
After rollback: users on v3 get "moved back" to v2's code. Users already on v2 see no update (same hash).
Target a Specific Release
npx turbopush rollback myapp-ios Production --targetRelease v34
Rollbacks are marked in deployment history output.