fix: lock Chrome version to 126

[HowardBraham]

Description

Chrome version 127 is causing problems on CircleCI. This temporarily locks the Chrome version to 126.

Related issues

Manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

• [x ] I've followed MetaMask Contributor Docs and MetaMask Extension Coding Standards.
• I've completed the PR template to the best of my ability
• I’ve included tests if applicable
• I’ve documented my code using JSDoc format if applicable
• I’ve applied the right labels on the PR (see labeling guidelines). Not required for external contributors.

Pre-merge reviewer checklist

• I've manually tested the PR (e.g. pull and build branch, run the app, test code being changed).
• I confirm that this PR addresses all acceptance criteria described in the ticket it closes and includes the necessary testing evidence such as recordings and or screenshots.

[github-actions]

CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes.

[greptile-apps]

PR Summary

Temporarily locked the Chrome version to 126 to address issues with Chrome 127 on CircleCI.

• Modified test/e2e/webdriver/chrome.js to set the Chrome version to 126.
• Ensures stability in the CI environment by avoiding issues with Chrome 127.
• No security issues or logical errors introduced.
• This is a temporary fix and should be revisited once Chrome 127 issues are resolved.

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[hjetpoluru]

LGTM

[metamaskbot]

Builds ready [3e1060b]

• builds: chrome, firefox
• builds (beta): chrome
• builds (flask): chrome, firefox
• builds (MMI): chrome, firefox
• builds (test): chrome, firefox
• builds (test-flask): chrome, firefox
• build viz: Build System
• mv3: Background Module Init Stats
• mv3: UI Init Stats
• mv3: Module Load Stats
• mv3: Bundle Size Stats
• mv2: E2e Actions Stats
• code coverage: Report
• storybook: Storybook
• typescript migration: Dashboard
• all artifacts
• bundle viz:

  • background: 0, 1, 2, 3, 4, 5
  • common: 0, 1, 10, 2, 3, 4, 5, 6, 7, 8, 9
  • content-script: 0
  • offscreen: 0
  • ui: 0, 1, 10, 11, 2, 3, 4, 5, 6, 7, 8, 9

Page Load Metrics (222 ± 216 ms)

Platform	Page	Metric	Min (ms)	Max (ms)	Average (ms)	StandardDeviation (ms)	MarginOfError (ms)
Chrome	Home	firstPaint	70	142	102	24	11
		domContentLoaded	9	69	25	17	8
		load	41	1575	222	451	216
		domInteractive	9	69	25	17	8

Bundle size diffs

• background: 0 Bytes (0.00%)
• ui: 0 Bytes (0.00%)
• common: 0 Bytes (0.00%)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 69.67%. Comparing base (3d2a436) to head (3e1060b).

Additional details and impacted files

@@           Coverage Diff            @@
##           develop   #26101   +/-   ##
========================================
  Coverage    69.67%   69.67%           
========================================
  Files         1405     1405           
  Lines        49728    49728           
  Branches     13748    13748           
========================================
+ Hits         34645    34646    +1     
+ Misses       15083    15082    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[metamaskbot]

Missing release label release-12.0.0 on PR. Adding release label release-12.0.0 on PR and removing other release labels(release-12.3.0), as PR was cherry-picked in branch 12.0.0.