Releases and rollback. Every deploy is a release you can go back to in seconds.

Every deploy, rollback and environment change makes a release: a number, why it was made, who made it, and the build it runs.

hub app my-app releases        # newest first, * marks the one running
hub app my-app rollback        # the newest earlier release that ran
hub app my-app rollback 4      # release 4

A rollback makes a new release that runs the build of the release you name, with today's environment. It skips the build, so it takes seconds, and it changes the code only. The release that runs now keeps serving until the one you roll back to answers.

Hub keeps the last 5 builds of each instance on your host. An older release fails with "that release is no longer on the host; deploy again". A release that never ran cannot be a rollback target.

Redeploy

hub app my-app redeploy

For an app connected to GitHub, redeploy deploys the branch head. For an uploaded app, it builds the current release's upload again. Both make a new release.

On the dashboard

The Deploys page of each instance lists its releases with their number, status, kind, commit, author and time. A number opens that release with its whole build log, which updates every 2 seconds while the release builds.