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

Jump to bottom

Upgrade manifest version to v3 #54

Open
jeroenheijmans opened this issue Dec 2, 2021 · 5 comments
Open

Upgrade manifest version to v3 #54

jeroenheijmans opened this issue Dec 2, 2021 · 5 comments
Labels
enhancement Improve an existing feature. requires investigation Something still to be investigated

Comments

@jeroenheijmans
Copy link
Owner

Still using manifest_version: 2 and I think Chrome and Firefox will be requiring v3 soon. Let's upgrade, hopefully it's easy.
@jeroenheijmans jeroenheijmans added the enhancement Improve an existing feature. label Dec 2, 2021
@jeroenheijmans jeroenheijmans self-assigned this Dec 2, 2021
@jeroenheijmans
Copy link
Owner Author

Fixed in 7df84a1 (I hope....)

@jeroenheijmans
Copy link
Owner Author

Oh whelp, Firefox actually does not allow v3 yet:

image

That's sad. I'll create a temp release for Firefox then.

jeroenheijmans added a commit that referenced this issue Dec 2, 2021
@jeroenheijmans
Firefox requires v2 manifests
0338c86 
See also: #54 (comment)
See: #54

Creating a branch with manifest-v2-based releases specially for
Firefox.
@jeroenheijmans
Copy link
Owner Author

jeroenheijmans commented Jan 7, 2023 •
edited

This is still the case. And I also think I've read that V3 rollout on Chrome isn't smooth either? I'm rolling back to v2 in #79 (2023 updates) until v3 is supported everywhere (or v2 is not supported anymore in Chrome or Firefox).

Reopening this issue until we can actually fix this.

EDIT: From https://developer.chrome.com/blog/more-mv2-transition/

December 9, 2022: The Manifest V2 deprecation timelines are under review and the experiments scheduled for early 2023 are being postponed. For more information, read the update in the chromium-extensions Google Group.

@jeroenheijmans jeroenheijmans reopened this Jan 7, 2023
@jeroenheijmans jeroenheijmans added the requires investigation Something still to be investigated label Jan 7, 2023
@jeroenheijmans jeroenheijmans mentioned this issue Jan 7, 2023
Merged
@jeroenheijmans jeroenheijmans removed their assignment Jan 7, 2023
@jeroenheijmans
Copy link
Owner Author

Note that this is still on hold, Chrome is as far as I know still mucking about with the V3 thing so as long as it's not strictly necessary I will not move this extension over.

I'll leave this issue open for visibility and further updates.

@jeroenheijmans
Copy link
Owner Author

Google sent out this e-mail:

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.

  • The Google Chrome Web Store team

So it seems we're good for the 2023 edition, and will have to see what happens between now and the 2024 (!?) AoC edition.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement Improve an existing feature. requires investigation Something still to be investigated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jeroenheijmans