Theme deployments
See your theme's deployment history and roll back to a previous version if you need to
A theme deployment is a moment when a new version of your theme was applied to your site. Every theme update — whether it added new blocks, updated styles, fixed a bug, or changed settings — produces a deployment record. Together they form the history of your theme on this site.
Open Themes under Design to find deployment history and rollback actions on the relevant theme.
What the deployment history shows
Each deployment record includes:
- When the deployment happened.
- Who deployed it (your theme developer, an automated build, or a Basker admin user).
- What changed at the level the system can see — manifest differences, block changes, template changes, settings changes.
- The previous theme version the deployment replaced.
The list reads as a reverse-chronological audit log of every theme update.
Rolling back
If a deployment caused an issue you can't immediately fix, roll back to the previous version. Open the deployment history, select the previous version, and confirm the rollback.
A rollback is itself a deployment — it produces a new entry in the history rather than removing the bad one. This means you have a full record of what happened, including the reverted update.
After a rollback, coordinate with your theme developer on the underlying fix. Roll forward to a new corrected deployment when it's ready.
When to roll back versus push a fix
- Roll back when the issue is broad — visible site-wide, affecting many pages, blocking visitors. Safety comes first.
- Push a fix when the issue is narrow and fixable within a short window. A quick patch is preferable to a rollback that pulls back unrelated improvements with it.
Speak to your theme developer if you're unsure.