PSA: Version rollbacks in the Chrome Web Store Developer Dashboard 🚀

646 views
Skip to first unread message

Chromium Extensions

unread,
Apr 9, 2024, 1:38:36 PMApr 9
to Chromium Extensions

Hey everyone,


I’m happy to announce that we’ve started rolling out a heavily requested feature that lets you roll back your extension to the previous published version in the Chrome Web Store - without additional review! The feature should be available to everyone by the end of the day. Read the full announcement in our blog post for more detail.


Cheers,


Sebastian from the Chrome Extensions DevRel team


Robert James Gabriel

unread,
Apr 9, 2024, 1:48:23 PMApr 9
to Chromium Extensions
Omg!!!
Thank you
Robert James Gabriel

On Apr 9, 2024, at 12:38, Chromium Extensions <chromium-...@chromium.org> wrote:


--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/67757bc9-bb7c-482e-a08d-c8219d2131e3n%40chromium.org.

Roberto Oneto

unread,
Apr 10, 2024, 3:06:36 AMApr 10
to Chromium Extensions, Robert James Gabriel
It's excellent news!
It would also be very useful to be able to ask for the interruption of the review process if this has not already gone too far.
It would avoid many cases of rollback.

Sean Gates

unread,
Apr 10, 2024, 10:57:16 AMApr 10
to Chromium Extensions
Amazing! Thanks! We've needed this for a while.

Sean Gates

unread,
Apr 15, 2024, 11:13:35 AMApr 15
to Chromium Extensions, Sean Gates
We rolled back, but now we can't publish a new version! We need help ASAP!

Previous version (with the issue in it): 1.2.0
Current version (after roll back): 1.2.1
Draft version: 1.2.2

Thanks!
– Sean

Patrick Kettner

unread,
Apr 15, 2024, 11:19:33 AMApr 15
to Sean Gates, Chromium Extensions
Hey Sean!
Was this for ofpfbinbikpbeicmdeciloaebgckpoli? I don't see a version in draft for you. What are you seeing? What is happening when you try to publish?

Oliver Dunk

unread,
Apr 15, 2024, 11:19:52 AMApr 15
to Sean Gates, Chromium Extensions
Hi Sean,

Can you clarify what you are seeing?

Are you unable to submit for review for some reason, or are you just asking if there is a way to expedite the process?
Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB


Sean Gates

unread,
Apr 15, 2024, 12:00:17 PMApr 15
to Oliver Dunk, Chromium Extensions
Crisis averted. I'm also working with Oliver and Patrick on improvements to the UX so that we all can benefit.

For everyone's benefit:

If you roll back you create a version number going forward in semver. When you upload a new package after this, going forward in semver, you must manually click "Save Draft".

I was missing this as a step since all previous uploads of a new package resulted in the draft being automatically saved. I've been discussing with Oliver and Patrick about the changed behavior and hopefully they can address it.

--
Sean Gates, CTO

Artem from bardeen.ai

unread,
Apr 16, 2024, 5:12:41 AMApr 16
to Chromium Extensions
Hey Folks,

I just tried using this, and I am only able to roll back to one previous version that was *fully rolled out*. So I am on the version 2.50.0, my previously published version was 2.48.0 (rolled out to only 10% of the users), but the only rollback version I am seeing is 2.46.0 (which was the version before 2.48.0 and was rolled out to 100%). Is this by design?

Artem.

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/67757bc9-bb7c-482e-a08d-c8219d2131e3n%40chromium.org.


--
Co-Founder and CTO bardeen.ai

Oliver Dunk

unread,
Apr 17, 2024, 7:01:55 AMApr 17
to Artem from bardeen.ai, Chromium Extensions
Hi Artem,

That is the expected behavior. I appreciate that having slightly more flexibility might be nice in the future - but we very much wanted to avoid perfect being the enemy of good and scope an MVP that we could ship sooner rather than later :)

There are some technical restrictions on our side that make it hard to provide more control, but it's something we're open to down the road.

In the meantime, we just updated our documentation to make this clearer. Thanks for the feedback!

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

Jason Wilson

unread,
Apr 23, 2024, 4:55:55 PMApr 23
to Chromium Extensions, Oliver Dunk, Chromium Extensions, Artem from bardeen.ai
Would this also apply to manifest V2 to V3 versions if we discover a critical issue? We're trying to vet our conversion as much as possible before flipping the switch, but it would be nice to know if we could rollback temporarily to V2 if a significant issue arose.

Patrick Kettner

unread,
Apr 24, 2024, 8:09:57 AMApr 24
to Jason Wilson, Chromium Extensions, Oliver Dunk, Artem from bardeen.ai
Hi Jason!
There is no restriction to rollback between manifest versions. 

patrick

muzuiget

unread,
Apr 26, 2024, 3:03:15 PMApr 26
to Chromium Extensions, Chromium Extensions
Hi CWS developers,

After reading the rollback documentation, I still have some questions.

Why do rollbacks need to provide a new version number?

Does this mean there is no "real rollback"? Does CWS just pick the previous version's .crx file, change the version field in the manifest.json file, and then repackage it into a new .crx file?

For example:

1. the developer have published version `1.0`.
2. the developer have published version `1.1`. It has bugs.
3. the developer rollback to `1.0`, providing a new version number `1.2`.

Does this mean that the version number `1.2` is occupied? The next time the developer releases a new version normally, will the version number need to be `1.3`, and cannot be lower than `1.2`?

If I enter the wrong rollback new version number like `100.0`, does this mean my next new version number can only be greater than `100.0` forever?

Yeferson Licet

unread,
Apr 26, 2024, 3:57:06 PMApr 26
to Chromium Extensions, muzuiget, Chromium Extensions
That's great! Thank you for this, anyone else seeing 0 in past days stats?

PhistucK

unread,
Apr 27, 2024, 3:02:19 PMApr 27
to muzuiget, Chromium Extensions
Probably to simplify the version management within Chrome, which only updates to a greater version than the currently installed version at the moment.

Yes, the next version will have to be greater than 1.2/100 forever, I believe.

PhistucK


--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.

Oliver Dunk

unread,
Apr 29, 2024, 5:42:35 AMApr 29
to PhistucK, muzuiget, Chromium Extensions
Hi muzuiget,

PhistucK is correct, incrementing the version number is a requirement based on how Chrome handles updates. They do always need to be increasing so you should be careful that you don't pick anything too high, like 100, when performing a rollback in the UI.

This feels very similar to uploading a new version of course, but the big difference is the lack of review :)

Oliver Dunk | DevRel, Chrome Extensions | https://developer.chrome.com/ | London, GB

Reply all
Reply to author
Forward
0 new messages