Before you roll back, read the commits
3 min read
Something broke right after a deploy, and the quick fix is to put the previous one back. Most hosts make that one click. What they don't show is everything else that goes with it. If two people merged since the deploy you're returning to, rolling back undoes their work too, and one of those commits might be the fix someone shipped an hour ago.
Deploys with their commits
The Deployments page lists recent deploys from every host the project connects: Vercel, Netlify, Render, Cloudflare Workers and Expo. Each row shows the commit message it was built from, its branch and target, its state, and a Live badge on the one serving right now.
What making it live would change
Open Changes on a deploy that isn't live and Baseboard asks your source connection to compare it with the live one. You get two lists. The first says "Making this live undoes 3 commits" and names them. The second shows the commits it would add that aren't live yet. Each commit has its short SHA, title, author and time, with a link to the forge where there is one.
On the live deploy, Changes shows what it shipped since the previous deploy on the same target.
The comparison works with GitHub, GitLab, Bitbucket, Gitea or Forgejo, and any Git remote over HTTPS. For a long range the forge may send back only part of it; Baseboard says so and links to the full comparison where the forge has one.
There's one gap. A deploy needs a recorded commit for any of this, and Cloudflare Workers versions don't record the commit they were built from. Those rows have no Changes button.
Making it live
Hosts have their own rules about which deploys they'll serve again, so Make live only appears where the host will accept it. On Render that's a deploy that was live once and was later replaced. On Netlify it's a ready production deploy.
Clicking it asks you to confirm, naming the host, the deploy and its id, and warns that it runs straight away and can't be undone from Baseboard.
Who can press it
A rollback is a change, so it's off for everyone until an owner allows it. In the permissions editor it's called Promote deployment. Owners start without it too and have to allow it for themselves. The Free plan is read-only, so rollbacks need Pro or Team. An access token with the Change scope can roll back as well, but only where the member who made it is allowed to.
Every rollback lands in the audit log with who made it. The Deployments page shows the list, the commits and the button on one screen.