Rolling back a release

Rollback returns a deployment to an earlier release:

aether rollback MyApp Production

Without a target it goes back to the release before the current one. To land on a specific version:

aether rollback MyApp Production --targetRelease v4

Rollback creates a release, it deletes nothing

The server copies the target release into a brand-new release at the head of the history, with a new label, releaseMethod: Rollback, and originalLabel pointing at the release it restored. History stays complete: you can see the bad release, the rollback, and everything before them.

Because it is a normal new release, devices pick it up through the standard update flow. The new release starts enabled and with no rollout limit, so every device that checks in gets it.

Guards

The server refuses to:

• Roll back to the release that is already the latest.
• Roll back across app versions: the target must have the same target binary version as the current release, so devices on the current binary can actually run what you restore.

Client-side rollback is different

The SDK also rolls back on its own when an update crashes before it confirms itself. That mechanism is per-device and automatic; this page covers the server-side operation you run on a whole deployment. The update lifecycle page covers the client side.