There are two key dates for the phase-out:
--
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/CAFY0HLPUwDSK6Ef_uS%3DhaF73_dKOLd5g0anPUPOE-LTcBZia%3Dw%40mail.gmail.com.
Now I feel like an idiot for insisting on starting MV3 dev in earnest at our company (given that the last timeline guidance suggested MV2 would be totally dead in Jan 2022).But this is a good outcome altogether, because MV3 definitely needs a lot of work in order to be feasible without a lot of hacky workarounds that upset users.On Thu, Sep 23, 2021 at 10:34 AM Simeon Vincent <sim...@chromium.org> wrote:Greetings extension devs,
Today the Chrome extensions team just published a blog post announcing the Manifest V2 deprecation timeline. From the blog post:There are two key dates for the phase-out:
- January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store. Developers may still push updates to existing Manifest V2 extensions, but no new Manifest V2 items may be submitted.
- January 2023: The Chrome browser will no longer run Manifest V2 extensions. Developers may no longer push updates to existing Manifest V2 extensions.
The full timeline, including enterprise-related information, is available on the Manifest V2 support timeline page. That page will be kept up to date with relevant changes or modifications to the sunset process.
I'm looking forward to continuing further improving our migration resources and extension developer guidance. If you have any suggestions on how we can help you and other developers navigate this transition, please let us know!
Simeon - @dotproto
Chrome Extensions DevRel
--
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-extensions+unsub...@chromium.org.
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/6b498c61-3907-41d2-a8d4-212a45a31063n%40chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extensions+unsub...@chromium.org.
and that Manifest V2 would stop working at the earliest in January 2022. - Simeon
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/CAFY0HLPUwDSK6Ef_uS%3DhaF73_dKOLd5g0anPUPOE-LTcBZia%3Dw%40mail.gmail.com.
--
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/ad9f7253-c1b6-41af-b5b1-aa34c241b89bn%40chromium.org.
--
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/887a9a66-7ff0-472d-bec7-73d37b1db2bcn%40chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/CAAgdh1%2Br7OfVBO-6TMBL-mFqrEHEjyExTEd0tSxL8OvTYW%3D%2BVg%40mail.gmail.com.
While there is not an exact date for removing support for Manifest V2 extensions, developers can expect the migration period to last at least a year from when Manifest V3 lands in the stable channel.
The W3C WebExtensions Community Group issue tracker is also a good place for raising these issues.For example, here is a list of problems with Service Worker-based extensions: https://github.com/w3c/webextensions/issues/72