Chrome Web Store to the previous version.

This page describes how to rollback an extension or theme ("item") to itsprevious version. Use this if you've released an extension update with bugs andwant to rollback to the earlier version immediately.

How does a rollback work?

The Chrome Web Store rollback feature lets you switch back to the previouspublished version. A rollback requires a new version number under which theprevious version of your extension will be re-published. For example, if thecurrent version of your extension is 1.1 and the previous version was 1.0, youcan rollback to the 1.0 version by providing a new version 1.1.

Once a rollback is initiated, the previous version becomes live on the Web Storewithin a minute. This step does not require any reviews. Once the previousversion is live on the Web Store, the normal extension update cycle applies. Toupdate your extension after a successful rollback, publish a new version as younormally would.

You can perform multiple rollbacks in a row. However, a rollback always switchesback to the previously published version. For example, after a rollback fromversion 1.1 to 1.0 (using new version 1.2), a subsequent roll back will switchback to version 1.1 (as a new version 1.3). This means, subsequent rollbackswill cycle between the same two versions of your extension.

Rollback during a percentage rollout

Performing a rollback during apercentagerollout will discard the partiallyrolled out version and will rollback to the previous published version that wasset to deploy to 100%. For example, if your extension with version 1.2 is rolledout at 1% and the previous version 1.1 is rolled out at 50%, triggering arollback will revert to the version 1.0 (if it was deployed at 100%) and therebyrevert and abort all ongoing percentage based rollouts.

Rollback with pending submissions

Any pending submissions will be discarded after a rollback. This includesstaged submissions and pendingreview submissions. For example, if your extension has version 1.2 pendingreview, version 1.1 published, and version 1.0 published before 1.1, then youcould roll back from 1.1 to 1.0. After doing that, the pending submission with1.2 will be discarded, and you'd need to resubmit 1.2 in order to publish it.

Ensure backward compatibility before triggering a rollback

A rollback has the potential to break your extension, or cause data loss. If youwant to benefit from the ability to quickly roll back to a previous version ofyour extension, make changes in a way that leaves the data needed by earlierversions intact. In particular, avoid making breaking changes to any stored datarequired by the previous version of your extension. Always test the rollbacklocally, before triggering it in the Developer Dashboard.

Trigger a rollback

There are two ways to trigger a rollback.

1. You can trigger a rollback by clicking⋮ View more menu options:

2. A rollback can also be triggered on theBuild > package page of yourextension by clickingRoll back to previous version:

A rollback requires a new version number under which the previous version ofyour extension will be re-published and a reason for the rollback. Fill in therequired information and confirm the roll back:

Then, selectRoll back and wait for the "Rolled back successfully"notification to show up.

Verify the rollback was successful

There are different ways to verify if a rollback has been performedsuccessfully:

1.Build > Package in the Developer Dashboard should list the previousversion of your extension under with the new version number.

2.Build > Status in the Developer Dashboard will show a message describing

3.Item details page in the Web Store will list the new version afterseveral minutes.