4 ms·
~$ cat /etc/chromium/policies/managed/ubo-policies.json { "ExtensionManifestV2Availability": 2 } Will save you for another year.
by cwillu 2y ago
~$ cat /etc/chromium/policies/managed/ubo-policies.json
{
"ExtensionManifestV2Availability": 2
}
Will save you for another year.
- kkfx 2y agoIf I recall correctly only till June 2025, did they change the date?
- alihm 2y agoI'm not sure but a lot of people hypothesize that they will have to keep this feature for enterprise customers (not for UBO but other custom enterprise extensions that use manifest v2)
- chii 2y agothey can easily just blacklist ubo if they really wanted to remove it. And they can make it plausibly deniable - by blacklisting the extension id of anything that is in the chrome extension store that originally had manifestV2 (which will have some collateral damage, but obviously google doesn't care).
- anticensor 2y agoBut that would also harm companies that actually intend to switch to a v3 based replacement but need a bit of time to complete the development.
- chii 2y agoThat's what the registry entry for the manifestV2 time extension is for - this was actually known for several years already, and 2025 june is meant to have been the deadline for that development.
- pieter_mj 2y agoIn windows start regedit as administrator and navigate to/create HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome. Under the Chrome key, create a DWORD value named "ExtensionManifestV2Availability" with hex value 2. Restart Chrome. If successful, you'll notice the ExtensionManifestV2Availability entry with value 2 in chrome://policy and the settings page will mention "managed by your organization".