As new listings for MV2 extensions can no longer be created in the Chrome Web Store, I wanted to ensure that it will still be possible to change a listing that was originally MV2 but updated to MV3, back to MV2 if needed.The concern arises from the scenario that we would like to replace our MV2 extension with one that is MV3 compatible later this year, but release very incrementally using the staged rollout feature. As we wouldn't yet be forced to ship an MV3 compatible extension at this time, if any substantial enough anomalies are detected during the staged rollout to MV3, we want to make sure we have the ability to roll back the extension to MV2 if needed.
--
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/3bd72faf-b253-4c08-9844-81fa2d0f640cn%40chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/f9243f76-7a0a-4462-ab27-0635bd435c45n%40chromium.org.
I'm writing to confirm our understanding of how the 0% rollout works for our unlisted Chrome extension update (version 2.3 to 3.0):
Could you please confirm if this understanding is correct?
Specifically, we want to verify that trusted testers will not receive version 3.0 while rollout remains at 0%.
Thank you so much for your help.
Best regards,