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.

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

Remove Manifest V2 support #1210

Closed
4 tasks
robertknight opened this issue Apr 19, 2023 · 0 comments · Fixed by #1418
Closed
4 tasks

Remove Manifest V2 support #1210

robertknight opened this issue Apr 19, 2023 · 0 comments · Fixed by #1418

Comments

@robertknight
Copy link
Member

As part of the migration to Manifest V3 we added a build config option (manifestV3) to support building as either MV2 or MV3. We have now changed our production extension over to MV3. Once we are sure that we don't need MV2 any more, we should remove the code.

  • Make the manifestV3 build option the default behavior
  • Remove the manifestV3 build option
  • Remove code paths in eg. chrome-api.ts that support Manifest V2
  • Find remaining references to Manifest V2 in the code and delete them
robertknight added a commit that referenced this issue Nov 30, 2023
Remove support for building the extension using Manifest V2. We've been shipping
our extension as Manifest V3 since April 2023 and have not encountered any
issues. Removing Manifest V2 support will simplify future development.

Fixes #1210
robertknight added a commit that referenced this issue Nov 30, 2023
Remove support for building the extension using Manifest V2. We've been shipping
our extension as Manifest V3 since April 2023 and have not encountered any
issues. Removing Manifest V2 support will simplify future development.

Fixes #1210
robertknight added a commit that referenced this issue Dec 1, 2023
Remove support for building the extension using Manifest V2. We've been shipping
our extension as Manifest V3 since April 2023 and have not encountered any
issues. Removing Manifest V2 support will simplify future development.

Fixes #1210
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant