[PSA] Chrome Extension Manifest V2 to V3 Migration
Terry Yan
TL;DR
Chrome extensions will be migrated from Manifest V2 to V3 in June 2025. Therefore, all manifests used by Tast need to be migrated.
Overview
With the impending deprecation of Chrome Extension Manifest V2 in June 2025, we are initiating the migration of Chrome extensions used within the Tast tests and Autotest testing framework to Manifest V3. Manifest V3 represents a significant evolution of the Chrome extension platform, introducing enhancements in performance, security, and privacy.
This migration addresses critical areas, including:
Manifest Updates: The manifest.json file will undergo structural and content changes, including updating manifest_version, modifying background script declarations (using service workers), and potential permission adjustments, etc.
Service Workers: Manifest V3 replaces background pages with service workers, affecting how extensions manage background processes and interact with the browser. This requires the behavior enhancement needed for the test connection, making sure test cases can identify the correct target to connect to after Manifest V3.
API Modifications: Several APIs have been modified or replaced in Manifest V3, need reviews and updates to relevant APIs used within ChromeOS. For more information please see replace unsupported APIs
Alternative Extensions: For extensions that are currently not supported by V3 but are critical for the ChromeOS testing process, alternative non-Chrome extension methods are required, ensuring the integrity of the tests.
Deprecated Features: Features and tests that depend on extensions that are no longer supported by V3 will be disabled if no alternatives are found.
This migration is critical to maintaining the stability of ChromeOS testing. We will closely monitor test results throughout the migration process and address any potential issues promptly. Teams should be aware of the potential impact of this migration and adjust testing procedures as needed.
Related Actions and Information
For detailed please see go/cros-extension-manifest-upgrade-v3
Expect potential instability in test results during the migration.
For chrome developers site’s information regarding the deprecation timelines related to manifest V2, see Manifest V2 support timeline.
Teams who own the extensions still using Manifest V2 must complete the migration to manifest V3 before the deadline above, e.g: