[desrosj]

Backport of the runner update in #15518 to the 6.4 branch.

Changes

• Changes the GitHub-hosted Ubuntu runners used by this branch's workflows from ubuntu-latest to ubuntu-26.04, matching trunk. GitHub is moving ubuntu-latest from 24.04 to 26.04 between 2026-10-19 and 2026-11-19.
• Pins windows-latest to windows-2025 and macos-latest to macos-15, matching trunk, in a separate commit. windows-latest already points to windows-2025, so the Windows jobs are unchanged. macos-latest currently points to macos-26, so the macOS jobs move to the version used by trunk and 6.8+.
• Updates @playwright/test from 1.49.1 to 1.64.1, matching trunk. 1.49.1 still works on Ubuntu 26.04 (it falls back to the 24.04 browser build), so this is not required on this branch. It keeps a single Playwright version across trunk and all branches that use it.

The Playwright changes are in their own commit so they can be reviewed separately.

Playwright 1.49.1 → 1.64.1 review

• Lockfile: only @playwright/test, playwright and the playwright-core copy nested under playwright change, each to 1.64.1. Nothing else moves.
• Older copy: @wordpress/scripts 26.13.13 still depends directly on playwright-core 1.32.0. wp-scripts test-playwright only uses that copy to install browsers before the run; the tests run on 1.64.1. This was already the case with 1.49.1, so it isn't a regression.
• Test discovery: playwright test --list finds the same tests before and after: e2e 20, performance 40, visual-regression 22.
• API changes: none of the removed or changed APIs in the 1.50–1.64 release notes are used by this branch's tests, its configs, or @wordpress/e2e-test-utils-playwright 0.10.13.
• Requirements: 1.64.1 requires Node >=20, and this branch uses Node 20.
• Visual changes: 1.64 forwards the 1920×1080 screen from devices['Desktop Chrome'] in the @wordpress/scripts base config, and 1.57 switched Chromium to Chrome for Testing builds. Either could change toHaveScreenshot output, but the visual regression suite isn't run in CI and has no committed baselines. If the old screen behaviour is needed, add screen: undefined to the config's use.

Trac ticket: Core-66499

Use of AI Tools

Claude Code (Claude Opus 5.5) made these changes, reviewed the Playwright update, ran the fork-based test runs, and drafted this description. Draft PRs should be considered unverified and unreviewed by a human.

🤖 Generated with Claude Code

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props desrosj.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[lancewillett]

Checked against the branch's workflows: every ubuntu-latest label is now ubuntu-26.04, Windows and macOS are pinned to windows-2025 and macos-15 as in #15518, and Playwright is 1.64.1 (the branch is on Node 20, which it needs). CI is green (50 passed, 14 skipped). Reusable workflows on this branch run from trunk, so the jobs that use them still ran on ubuntu-24.04 here. Please land #15518 first, then this.

_{AI review · claude-opus-5-5}