Skip to content

fix(deps, ci): bump playwright to 1.64.1 for Ubuntu 26.04 - #9091

Closed
aglinxinyuan wants to merge 2 commits into
apache:mainfrom
aglinxinyuan:fix/ci-playwright-ubuntu-2604
Closed

aglinxinyuan wants to merge 2 commits into
apache:mainfrom
aglinxinyuan:fix/ci-playwright-ubuntu-2604

Conversation

@aglinxinyuan

@aglinxinyuan aglinxinyuan commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

What changes were proposed in this PR?

GitHub has started moving ubuntu-latest runners to the Ubuntu 26.04 image (Image: ubuntu-26.04, version 20261012.601). On those runners, build / frontend (ubuntu-latest, 24.19.0) fails at Install Playwright Chromium, before any test runs:

Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64

The rollout is gradual, so it hits a random subset of runs: main's last ubuntu frontend run (2026-10-21) still landed on 24.04 and passed, while #9088's run on 2026-10-22 landed on 26.04 and failed. Nothing in the repository changed.

The cause is the pinned playwright 1.59.1, which predates Ubuntu 26.04 support. 1.61.0 is the first release whose host-platform detection and browser registry know ubuntu26.04. This bumps playwright to 1.64.1 (the current release, and the version Renovate's grouped #7896 also targets), with the lockfile regenerated by the vendored Yarn 4.14.1:

  • playwright / playwright-core: 1.59.1 → 1.64.1.
  • fsevents@2.3.2 drops out of the lockfile; it was an optional macOS dependency of the old playwright only.

@vitest/browser-playwright 4.1.11 declares playwright: "*" as its peer, and playwright is a dev dependency, so no LICENSE-binary entry changes.

release/v1.2 and release/v1.3 pin the same playwright 1.59.1 and run the same install step, and the change applies to both cleanly, so this carries their backport labels. release/v1.1 does not use Playwright.

Any related issues, documentation, discussions?

No issue filed — the regression originates outside the repository and this PR is the unblock, as with #7710 and #9064.

How was this PR tested?

The failure itself depends on which runner image GitHub assigns, so it cannot be reproduced on demand here or locally. The bump was checked locally on Windows, from frontend/:

  • node .yarn/releases/yarn-4.14.1.cjs install --immutable --inline-builds: success.
  • node .yarn/releases/yarn-4.14.1.cjs playwright install chromium: downloads Chrome Headless Shell 156.0.8078.4 (playwright build v1248).
  • node .yarn/releases/yarn-4.14.1.cjs ng run gui:test-browser: 3 files, 23 tests, all pass.

This PR's own CI then confirmed the fix on the new image: build / frontend (ubuntu-latest, 24.19.0) and both backport legs (release/v1.2, release/v1.3) ran on Image: ubuntu-26.04 and passed, including the Install Playwright Chromium step.

Was this PR authored or co-authored using generative AI tooling?

Generated-by: Claude Code (Claude Opus 5.5)

🤖 Generated with Claude Code

ubuntu-latest runners are moving to the Ubuntu 26.04 image, where
playwright 1.59.1 refuses to install Chromium ("Playwright does not
support chromium on ubuntu26.04-x64"), so the ubuntu frontend leg
fails before any test runs. 1.61.0 is the first release that knows
ubuntu26.04; bump to the current 1.64.1 and regenerate yarn.lock.
@aglinxinyuan aglinxinyuan added the release/v1.2 back porting to release/v1.2 label Oct 22, 2026
Copilot AI balanced review requested due to automatic review settings October 22, 2026 07:56
@aglinxinyuan aglinxinyuan added release/v1.3 back porting to release/v1.3 release/v1.2 back porting to release/v1.2 labels Oct 22, 2026
@aglinxinyuan aglinxinyuan self-assigned this Oct 22, 2026

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions github-actions Bot added dependencies Pull requests that update a dependency file fix frontend Changes related to the frontend GUI labels Oct 22, 2026
@github-actions

github-actions Bot commented Oct 22, 2026 •

Copy link
Copy Markdown
Contributor

Automated Reviewer Suggestions

Based on the git blame history of the changed files, we recommend the following reviewers:

  • No candidates found from git blame history.

@parshimers
parshimers self-requested a review October 22, 2026 15:18
@codecov-commenter

codecov-commenter commented Oct 22, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.31%. Comparing base (6cfcfb1) to head (9879970).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main    #9091      +/-   ##
============================================
- Coverage     92.34%   92.31%   -0.04%     
+ Complexity     5046     5045       -1     
============================================
  Files          1261     1260       -1     
  Lines         54117    53903     -214     
  Branches       6767     6725      -42     
============================================
- Hits          49973    49758     -215     
- Misses         2485     2486       +1     
  Partials       1659     1659              
Flag Coverage Δ *Carryforward flag
access-control-service 77.38% <0.00%> (ø) Carriedforward from 6a101ad
agent-service 99.16% <0.00%> (ø) Carriedforward from 6a101ad
amber 87.31% <0.00%> (-0.01%) ⬇️ Carriedforward from 6a101ad
computing-unit-managing-service 60.48% <0.00%> (ø) Carriedforward from 6a101ad
config-service 87.37% <0.00%> (ø) Carriedforward from 6a101ad
file-service 82.00% <0.00%> (ø) Carriedforward from 6a101ad
frontend 96.55% <0.00%> (-0.01%) ⬇️
notebook-migration-service 83.73% <0.00%> (ø) Carriedforward from 6a101ad
pyamber 98.53% <0.00%> (-0.05%) ⬇️ Carriedforward from 6a101ad
workflow-compiling-service 72.43% <0.00%> (ø) Carriedforward from 6a101ad

*This pull request uses carry forward flags. Click here to find out more.

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

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aglinxinyuan

Copy link
Copy Markdown
Contributor Author

Replaced by #9100

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file fix frontend Changes related to the frontend GUI release/v1.2 back porting to release/v1.2 release/v1.3 back porting to release/v1.3

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants