Versions and going back

Every deploy is a version you can return to.

Every deploy creates a new version and keeps the previous one. The Free plan keeps the last 10 versions; Personal and above keep 50.

Seeing versions

In the dashboard, open the app and choose Versions. Each row says when it was made and by whom ("by Claude", "by the dashboard"), whether it is live, and whether it changed the database. From a terminal: npx uarpie versions.

Going back

Click Go back to this version, or ask your AI. Going back is instant: the address simply points at the older version again. Nothing is rebuilt.

When the database changed

If a newer version changed the database's shape (added a table, renamed a column), the older code may not work with the newer data. The dashboard warns you before you go back. You have two choices:

• Code only (the default): the old version runs against the current data. Usually fine when the change only added things.
• Also restore data from that time: the database is restored from the snapshot taken just before that version's change. Anything written since is lost, so this asks for an explicit confirmation.

The restore never happens in place: the snapshot is restored into a fresh database and the app switches to it, and the previous database is kept for seven days.

Watching a deploy

Most people never need to. For those who want to: each version has a trace, reachable from Versions ("See the trace") or from the Updating... banner while a deploy is running. It shows each step with its timing, and the build output as it happens. If a deploy failed, the trace opens with What happened and the fix first, and the raw output below it.