enjoy!
A broken update just went live and your users are feeling it. Before rollback existed, you'd have to fix the bug, resubmit, and wait days for review. Now you can revert in minutes.
The rollback feature re-publishes your previous version under a new version number — and skips the review queue because that code already passed review.
How to Rollback
- Open the Chrome Web Store Developer Dashboard.
- Select the broken extension.
- Click the three-dot menu on the listing, or go to Build > Package.
- Click Roll back to previous version.
- Enter a new version number (e.g., if the broken version is 2.5.0, use 2.5.1).
- Enter a reason for the rollback.
- Confirm.
The previous version goes live under the new version number. Verify under Build > Package that the old code is now active.
Good to Know
- One version back only. You can't skip back multiple versions. For anything older, manually re-upload the zip.
- Pending submissions get discarded. Anything in the review queue or staged for release is wiped when you rollback.
- Partial rollouts too. If you were at 30% rollout, rollback reverts everyone to the previous 100%-deployed version.
Cancel vs. Rollback
| Situation | What to do |
|---|---|
| Still in review, not yet live | Cancel the review |
| Already published and live | Rollback to previous version |
| Partial rollout going badly | Rollback (discards the partial rollout) |
| Need to go back 2+ versions | Re-upload the older zip manually |
Between cancel and rollback, you're covered for both "caught it early" and "it's already out there" scenarios.
For more Chrome Web Store tips, see how to cancel a submission.