Skip to content

Use Playwright 1.65.1, which supports Ubuntu 26.04 - #1400

Merged
clauderic merged 1 commit into
mainfrom
playwright-ubuntu-26
Nov 16, 2026
Merged

clauderic merged 1 commit into
mainfrom
playwright-ubuntu-26

Conversation

@clauderic

Copy link
Copy Markdown
Member

What are you adding in this PR?

GitHub is moving ubuntu-latest to Ubuntu 26.04, and CI fails on the jobs that land there, as on #1384:

.../@playwright/browser-chromium install: Error: ERROR: Playwright does not support chromium on ubuntu26.04-x64
ELIFECYCLE  Command failed with exit code 1.

pnpm install runs that install script, so the Linux jobs fail before any test runs, and fail-fast cancels the Windows ones. Jobs that still get ubuntu-24.04 pass, so it depends on the runner.

Playwright 1.65.1 supports ubuntu26.04-x64, and 1.60.0 doesn't. This changes the root pnpm.overrides from 1.60.0 to 1.65.1. The pin was added for 1.60.0's Node 24 extraction fix (2eeb81c), not to hold Playwright back.

Tophatting

On macOS with Node 24:

  • pnpm install --frozen-lockfile
  • CI's "Install Playwright browsers" step: @vscode/test-web resolves @playwright/browser-chromium 1.65.1.
  • pnpm build, then pnpm test:e2e: 3 passing.

I couldn't run it on Ubuntu 26.04 locally. This PR's CI only runs there if GitHub happens to give its jobs a 26.04 runner.

🤖 Generated with Claude Code

GitHub is moving `ubuntu-latest` to Ubuntu 26.04. On those runners, Playwright 1.60.0's
`@playwright/browser-chromium` install script throws "Playwright does not support chromium on
ubuntu26.04-x64", so `pnpm install` fails before any test runs. 1.65.1 supports ubuntu26.04.

The override pinned 1.60.0 for its Node 24 extraction fix (2eeb81c). It now pins 1.65.1.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@clauderic
clauderic requested a review from a team as a code owner November 16, 2026 16:08
@clauderic
clauderic merged commit 33cf4c9 into main Nov 16, 2026
8 checks passed
@clauderic
clauderic deleted the playwright-ubuntu-26 branch November 16, 2026 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants