Hi folks,
This is related to the updates yesterday on the MV2/MV3 timeline, and hopefully somebody here has the answer, or Simeon can chime in.
Consider this scenario:
- We have an MV3 extension as a separate unlisted BETA extension, it's working OK it seems (although there are some issues we are still concerned about)
- Some of our enterprise customers are still on old Chrome versions, ones before some very important MV3 platform issues were fixed. (We will communicate with them about updating, but I think it's clear not all of them will be able to or willing to)
- We would like to update our main, non-beta extension to MV3 soon (before January even)
At the moment, it would appear to me that I could update our main extension with the MV3 code, and include e.g. "minimum_chrome_version": "102.0.5005.61" in the manifest (that version is the first that had a bug fix that is important in our case).
If I were to do that, I believe that users who are still on older Chrome versions won't be able to install the extension at all (but if they already had it installed they would keep their older version of it).
Does anybody know if there is a way to publish an updated extension, set "minimum_chrome_version" in the manifest, and have users on older browsers receive the previous version of the extension instead?
It seems this would be quite a common case, and allowing older browsers to install a previous version of an extension (and update later) would be quite a necessary facility during the MV2->MV3 transition.
Cheers,
Jói