Skip to content

chore: roll Playwright to 1.65.0 (54575dd8ba) - #3345

Closed
microsoft-playwright-automation[bot] wants to merge 1 commit into
release-1.65from
roll-playwright-43485112775-1
Closed

microsoft-playwright-automation[bot] wants to merge 1 commit into
release-1.65from
roll-playwright-43485112775-1

Conversation

@microsoft-playwright-automation

Copy link
Copy Markdown
Contributor

Hi, I'm the Playwright bot. I prepared this release-1.65 roll.

  • Pin the driver to 54575dd8bafcf403382d645c75e572683e697679 on upstream release-1.65, and update the README to Chromium 159.0.8154.6.
  • Regenerate the API, protocol and test registry: no resulting changes. No Python client or test changes need porting; the driver supplies the updated device descriptors. Node.js stays at 26.13.1.
  • Left before this roll is complete: correct upstream test LO-193 and roll that correction. Both Python flavors fail its unchanged outline assertion: Chromium 158.0.8127.18 returns rgb(255, 0, 0) solid 3px, but 159.0.8154.6 returns 3px solid rgb(255, 0, 0). The upstream test has the same old expectation; this proposal does not change only the Python port to make it pass.
  • WebKit verification also needs a runner with complete browser dependencies. Local dependencies allowed page checks, but TLS checks remained blocked.
Upstream commits

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.

1 participant