Releases and rollback
How Aozumi releases replace each other, and how to roll back to an earlier healthy release in the same environment without rewriting history.
How releases replace each other
Every deploy creates a new release in one environment. The newest release decides where visitors go, and the release that is live now keeps serving until its replacement is ready. A failed or cancelled release never receives traffic, so a broken deploy leaves the previous release in place.
Roll back
- Open the Deployments tabFind the earlier release you want back.
- Choose Roll backConfirm when Aozumi asks.
- Follow the new releaseAozumi creates a new release from the one you picked. Nothing in the history is rewritten, so you can always see what ran and when.
Which releases qualify
- The release reached a healthy state.
- It belongs to the same environment.
- It is not already the current release.
- Its artifact is still available. Aozumi tells you when an old artifact has been cleaned up.
The console offers exactly the releases the API accepts, and explains why any other release cannot be restored.
Questions
- How do I roll back a deployment on Aozumi?
- Open the app's Deployments tab, find an earlier release that reached a healthy state in the same environment, and choose Roll back. Aozumi creates a new release from it; the release history is kept.
- Does rolling back restore my database?
- No. A rollback changes the running code and its release only. Database contents are restored separately with point-in-time restore.
Checked against the product on .