We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Chrome 127 (expected July 17th 2024) will probably disable manifest v2 extensions soon: https://developer.chrome.com/blog/resuming-the-transition-to-mv3 Before that date a manifest v3 version of the BPC-extension will be released for testing.
Pre-release Chrome version may block manifest v2 extensions sooner (June 2024): https://chromestatus.com/roadmap
By setting the ExtensionManifestV2Availability policy you can postphone this for a year though: https://chromeenterprise.google/policies/#ExtensionManifestV2Availability
Example ExtensionManifestV2Availability.reg file for Chrome main release:
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome] "ExtensionManifestV2Availability"=dword:00000002
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Chrome 127 (expected July 17th 2024) will probably disable manifest v2 extensions soon: https://developer.chrome.com/blog/resuming-the-transition-to-mv3
Before that date a manifest v3 version of the BPC-extension will be released for testing.
Pre-release Chrome version may block manifest v2 extensions sooner (June 2024): https://chromestatus.com/roadmap
By setting the ExtensionManifestV2Availability policy you can postphone this for a year though: https://chromeenterprise.google/policies/#ExtensionManifestV2Availability
Example ExtensionManifestV2Availability.reg file for Chrome main release:
The text was updated successfully, but these errors were encountered: