Repository navigation
fix(deps, ci): bump playwright to 1.64.1 for Ubuntu 26.04 - #9091
Closed
aglinxinyuan wants to merge 2 commits into
Closed
aglinxinyuan wants to merge 2 commits into
aglinxinyuan wants to merge 2 commits into
Conversation
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.
Contributor
Automated Reviewer SuggestionsBased on the
|
parshimers
self-requested a review
October 22, 2026 15:18
parshimers
approved these changes
Oct 22, 2026
Codecov Report✅ All modified and coverable lines are covered by tests. 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
*This pull request uses carry forward flags. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
aglinxinyuan
enabled auto-merge
October 24, 2026 03:21
aglinxinyuan
disabled auto-merge
October 24, 2026 03:21
aglinxinyuan
enabled auto-merge
October 24, 2026 05:03
aglinxinyuan
disabled auto-merge
October 24, 2026 05:03
Contributor
Author
|
Replaced by #9100 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this PR?
GitHub has started moving
ubuntu-latestrunners to the Ubuntu 26.04 image (Image: ubuntu-26.04, version20261012.601). On those runners,build / frontend (ubuntu-latest, 24.19.0)fails at Install Playwright Chromium, before any test runs: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
playwright1.59.1, which predates Ubuntu 26.04 support. 1.61.0 is the first release whose host-platform detection and browser registry knowubuntu26.04. This bumpsplaywrightto 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.2drops out of the lockfile; it was an optional macOS dependency of the oldplaywrightonly.@vitest/browser-playwright4.1.11 declaresplaywright: "*"as its peer, andplaywrightis a dev dependency, so noLICENSE-binaryentry changes.release/v1.2andrelease/v1.3pin the sameplaywright1.59.1 and run the same install step, and the change applies to both cleanly, so this carries their backport labels.release/v1.1does 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 onImage: ubuntu-26.04and 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