Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update manifest-v3.md from Jan to June #3041

Closed
wants to merge 5 commits into from
Closed

Update manifest-v3.md from Jan to June #3041

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
d91976d
Update manifest-v3.md
JesseHufstetlerNortridge Jan 31, 2024
eb67608
Rewrite article, update links per redirects
mikehoffms Feb 1, 2024
9f5ec3a
remove "note"
mikehoffms Feb 2, 2024
bf93d24
supported for Edge & P.C.
mikehoffms Feb 2, 2024
b5d3dbb
Merge branch 'main' into pr/3041
mikehoffms Feb 6, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 36 additions & 9 deletions microsoft-edge/extensions-chromium/developer-guide/manifest-v3.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,17 +6,23 @@ ms.author: msedgedevrel
ms.topic: conceptual
ms.service: microsoft-edge
ms.subservice: extensions
ms.date: 11/29/2022
ms.date: 02/01/2024
---
# Overview and timelines for migrating to Manifest V3

A manifest file is the blueprint of an extension. It includes information such as the version number of the extension, the title of the extension, and permissions needed to run the extension. Migrating from Manifest V2 to V3 will bring several structural changes to how extensions are handled by the browser.
A _manifest file_ is the blueprint of an extension. A manifest file for an extension includes information such as the version number of the extension, the title of the extension, and permissions needed to run the extension. The manifest file follows the format specified by Manifest V2 or Manifest V3. Support for Manifest V2 is being phased out.


<!-- ---------------------------------------------------------------------- -->
## Overview of changes in Manifest V3

Migrating from Manifest V2 to Manifest V3 will bring several structural changes to how extensions are handled by the browser.

In October 2020, Microsoft announced the [decision to embrace Manifest V3](https://blogs.windows.com/msedgedev/2020/10/14/extension-manifest-chromium-edge/) to help reduce fragmentation of the web for all developers and enhance privacy, security, and performance for end users.

Manifest V3 is an initiative of the [Chromium project](https://www.chromium.org/Home/).

An overview of the changes involved, as described in [Overview of Manifest V3 - Chrome Developers](https://developer.chrome.com/docs/extensions/mv3/intro/mv3-overview/):
An overview of the changes involved, as described in [Migrate to Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate):

* Service workers will replace background pages.

Expand All @@ -28,21 +34,42 @@ An overview of the changes involved, as described in [Overview of Manifest V3 -

* A number of minor feature improvements will also be introduced in Manifest V3.

To help you plan, consider the following schedule for Microsoft Partner Center and Microsoft Edge changes.

**We are currently in the process of updating our MV3 migration timelines.**
<!-- ---------------------------------------------------------------------- -->
## Manifest timeline for the Chromium browser engine

Chromium has revised the timelines for ending support for Manifest V2. See:

* [Manifest V2 support timeline](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline)
* [The phase-out timeline](https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline) in _Resuming the transition to Manifest V3_.


We are aware that Chromium has revised the timelines for Manifest V2 sunset. We will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here. We continue to analyze the concerns raised by the extension developers and explore the optimal path for Microsoft Edge Add-ons ecosystem. Meanwhile, please refer to the [Chromium timelines](https://developer.chrome.com/docs/extensions/mv3/mv2-sunset/) for planning your extension's migration.
<!-- ---------------------------------------------------------------------- -->
## Manifest timeline for Microsoft Edge and Partner Center

To help you plan the migration of your extension from Manifest V2 to Manifest V3, consider the following schedule for support for Manifest V2 and V3 in Microsoft Edge and Microsoft Partner Center.

The Microsoft Edge team will independently decide on MV3 migration timelines for Microsoft Edge Add-ons and share an update here. We continue to analyze the concerns raised by extension developers and explore the optimal path for Microsoft Edge Add-ons ecosystem. Meanwhile, to plan the migration of your extension from Manifest V2 to Manifest V3, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above.


**The Microsoft Edge team is currently in the process of updating this MV3 migration timeline.**

| Timeframe | Microsoft Partner Center changes | Microsoft Edge changes |
|--- |--- |--- |
| July 2022 (already in effect) | Microsoft Partner Center will no longer accept new Manifest V2 extensions with visibility set as `Hidden` or `Public`. | No change. |
| TBD - See note above | Microsoft Partner Center will no longer accept updates to existing Manifest V2 extensions. Developers can submit updates for migrating a V2 extension to V3. | Microsoft Edge stops running Manifest V2 extensions. Enterprises can allow Manifest V2 extensions to run on Microsoft Edge using Enterprise policies. |
| TBD - See note above | No change. | Manifest V2 extensions will no longer function in Microsoft Edge even with the use of Enterprise policies. |
| TBD | Microsoft Partner Center will no longer accept updates to existing Manifest V2 extensions. Developers can submit updates for migrating a V2 extension to V3. | Microsoft Edge stops running Manifest V2 extensions. Enterprises can allow Manifest V2 extensions to run on Microsoft Edge, by using enterprise policies. |
| TBD | No change. | Manifest V2 extensions will no longer function in Microsoft Edge, even with the use of enterprise policies. |

Manifest V2 extensions will continue to be supported through Enterprise policies at least until Chromium Manifest V2 support timeline (which is currently January 2024).
Manifest V2 extensions will continue to be supported at least until June 2024, in Microsoft Edge and Partner Center. Manifest V2 extensions will continue to be supported through enterprise policies at least until June 2025. For the latest dates in the Chromium Manifest V2 support timeline, see [Manifest timeline for the Chromium browser engine](#manifest-timeline-for-the-chromium-browser-engine), above.

Microsoft continues to iteratively improve the platform and address the feedback shared by extension developers.

Share your questions, comments, and concerns with the team on Twitter [@MSEdgeDev](https://twitter.com/msedgedev/) or via the [Microsoft Edge Insider forums on TechCommunity](https://techcommunity.microsoft.com/t5/articles/manifest-v3-changes-are-now-available-in-microsoft-edge/m-p/1780254).


<!-- ---------------------------------------------------------------------- -->
## See also

* [Migrate to Manifest V3](https://developer.chrome.com/docs/extensions/develop/migrate)
* [Manifest V2 support timeline](https://developer.chrome.com/docs/extensions/develop/migrate/mv2-deprecation-timeline)
* [The phase-out timeline](https://developer.chrome.com/blog/resuming-the-transition-to-mv3#the_phase-out_timeline) in _Resuming the transition to Manifest V3_.