#47972: build: check zip manifest for chromedriver.zip
Description of Change
Let's catch any potential regressions in the contents of chromedriver.zip by reusing our existing manifest approach.
Adding these manifests reveals some inconsistencies and potential things we may want to clean up, but I'd like to land the manifests first in this PR, and then follow-up with any cleanup in another PR. That way if the cleanup breaks anything and needs to be reverted, we don't also revert these manifests.
Checklist
- PR description included and stakeholders cc'd
Release Notes
Notes: none
Backports
No Backports Requested
This pull request doesn't have any backports requested or created for older release branches.
What are backports?
Backports are copies of changes made to the main branch that are applied to older release branches. They ensure that bug fixes and important changes are available in maintained older versions of Electron.
Semver Impact
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron