Setting the minimum chrome version when publishing a MV3 extension

[Jon Howard]

We're now getting close to releasing a major update (read rewrite from scratch) to our current MV2 extension which is fully MV3 compliant.

I've put the "minimum_chrome_version": "88" key in my manifest file and I want to check that this is enough to make sure that existing users (and any new users) who are running chrome 87 and below will continue to be served the legacy mv2 version and only be offered an update if and when they update to Chrome 88 or above.

Thanks

Jon...

[hrg...@gmail.com]

The web store can only distribute one version of your extension. If you set the minimum Chrome version to 88, then users running any previous browser version won't be able to install or update your extension.

MV3 is still quite buggy and incomplete, so it's not a good time to update your extension to MV3 yet.

It's better if you publish a separate extension as an MV3 beta and keep the MV2 version as the official/stable version.

[Browser Extenstion]

> separate extension as an MV3 beta and keep the MV2 version

This is a violation of CWS rules.

[hrg...@gmail.com]

On Friday, March 19, 2021 at 2:35:00 AM UTC-3 Browser Extenstion wrote:

> separate extension as an MV3 beta and keep the MV2 version

This is a violation of CWS rules.

 

It is not.

You can publish alternative versions of an extension if you state clearly that it's indeed a variant that's serves a different purpose. Such as a beta version that's meant for testing.

For example, Tampermonkey beta:

https://chrome.google.com/webstore/detail/tampermonkey-beta/gcalenpjmijncebpfijmoaglllgpjagf