Migrate to Manifest V3

[jamespizzurro]

Received this email from Google a few days ago:

Dear Developer,

You still have one or more published extensions currently running on Manifest Version 2, which has been deprecated. We recently announced the updated phase-out timeline of Manifest V2, and your item(s) will be impacted by these changes.

More specifically, if you have not migrated to Manifest V3 by June 2024, your Manifest V2 extension may begin to be disabled on Chrome browsers and the relevant item will lose its Featured badge in the Chrome Web Store if it currently has one.

Organizations using the ExtensionManifestV2Availability enterprise policy will continue to be able to run Manifest V2 extensions until June 2025.

We recommend completing the migration of your extensions to Manifest V3 before June 2024. Please consult the migration guide for help getting started, and if you have any questions, please reach out via our support channels.

Thank you for your cooperation and participation in the Chrome extension ecosystem.

I suspect will become easier through the use of better automated tools and documentation the closer we get to June 2024, but I wanted to create this issue now so that we don't forget about it if nothing else.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[jamespizzurro]

I received the following email from Google today:

Dear Developer,

As part of our ongoing efforts to enhance the security, privacy, and performance of the Chrome ecosystem, we are reaching out to inform you about upcoming changes to the Chrome Web Store's Featured badge criteria and item visibility for any remaining extensions built using Manifest Version 2 you have published.

Since the introduction of the Featured badge, we have recognized extensions that embrace technical best practices, offer superior user experiences, and maintain high standards of design. This badge reflects our commitment to promoting extensions that provide clear, helpful, and privacy-respecting experiences to users.

In line with our commitment to these values and the broader strategy to migrate toward more secure and performant extensions built using Manifest Version 3, we are updating the eligibility criteria for the Featured badge. On June 3rd, extensions must be built with Manifest Version 3 to qualify for or retain the Featured badge.

What this means for you:

Featured Badge Eligibility: To maintain your extension's Featured status, you will need to migrate it to Manifest V3 by June 3rd. In order to ensure sufficient time for extension review, we strongly advise finishing the migration to Manifest V3 weeks before this deadline. Extensions that do not complete this transition will see their Featured badge removed as part of our broader efforts to ensure a secure and up-to-date browsing experience for all Chrome users.
Visibility and Promotion: Manifest Version 3 extensions will be prioritized in the Chrome Web Store, including in search results and recommendations. This update aims to highlight extensions that align with our latest security standards and provide users with the best possible experience.
In-browser Phase-out: Beginning June of this year, we will begin to gradually disable extensions running Manifest V2 for Chrome users.
We encourage you to migrate your extension to Manifest Version 3. We understand that migrating to Manifest Version 3 represents a significant effort. This transition not only ensures that your extension can continue to be recognized as a Featured extension but also aligns with our shared goal of providing Chrome users with a secure, private, and high-performing browsing experience. To support you, we have compiled a suite of resources, guides, and tools available here. Our team is also available for consultations and assistance through the One Stop Support page.

Thank you for your cooperation and participation in the Chrome extension ecosystem.

Just another reminder that we need to do this.