chore(deps-dev): bump @playwright/test from 1.55.0 to 1.62.1 (#DS-5215) - #1850
Merged
Conversation
Resolves GHSA-7mvr-c777-76hp / CVE-2025-59288 (high): browsers were downloaded without verifying the SSL certificate, fixed in 1.55.1. The advisory had been parked in `npmAuditIgnoreAdvisories` precisely because the upgrade could not ride along inside an unrelated change; that entry goes away with it. 1.62.1 rather than the minimal 1.55.1: the screenshot cost is identical either way, since any release past 1.55.0 bumps the bundled Chromium and the baselines are compared with `threshold: 0`. Taking the latest buys seven minor releases for the same single regeneration. Bundled Chromium moves from 140.0.7339.16 to 151.0.7922.34, so all 215 committed screenshots are regenerated in this pull request via /approve-snapshots. None of the APIs removed between 1.56 and 1.62 are used here: the suite only touches `test`, `expect`, `Page`, `Locator`, `page.evaluate` and `toHaveScreenshot`. Verified locally against Chromium 151 and WebKit 26.5 — every failure is a screenshot mismatch (expected: the baselines are Linux), with no behavioural regression. In particular the clipboard round-trip in textarea still works under the headless clipboard isolation introduced in 1.62.
lskramarov
added
bug
|
Visit the preview URL for this PR (updated for commit e20a909): https://koobiq-next--prs-1850-uh1ze05s.web.app (expires Thu, 13 Aug 2026 06:44:15 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: c9e37e518febda70d0317d07e8ceb35ac43c534c |
🚨 E2E tests failedReview the report for details. 💡 Comment |
Contributor
Author
|
/approve-snapshots |
|
🔄 Updating snapshots. |
Contributor
There was a problem hiding this comment.
Pull request overview
Upgrades Playwright to resolve CVE-2025-59288 and align visual baselines with Chromium 151.
Changes:
- Bumps
@playwright/testand transitive packages to 1.62.1. - Removes the resolved audit exception.
- Clarifies screenshot-version pinning guidance.
Reviewed changes
Copilot reviewed 3 out of 4 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
package.json |
Updates the Playwright dependency. |
yarn.lock |
Locks Playwright packages at 1.62.1. |
.yarnrc.yml |
Removes the obsolete advisory exception. |
playwright.config.ts |
Refines baseline regeneration guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
✅ Snapshots updated! |
Contributor
|
Посмотрел, багов нет |
NikGurev
approved these changes
Aug 10, 2026
artembelik
approved these changes
Aug 10, 2026
lskramarov
added a commit
that referenced
this pull request
Aug 10, 2026
…311) @playwright/test moved to 1.62.1 on main in #1850, which this branch is now rebased onto. The `FROM` digest still resolved the v1.55.0-noble image, so playwright-core asked for chromium-1234, firefox-1538 and webkit-2336 while the image carried 1187, 1490 and 2203. Nothing silently degraded: tools/e2e/assert-browsers.js failed the build with that exact list, which is what it is there for. The digest below is what its own hint prints, `docker buildx imagetools inspect mcr.microsoft.com/playwright:v1.62.1-noble`. The baselines came along with the rebase — #1850 regenerated all 68 of them in the same commit as the version bump.
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.
Resolves GHSA-7mvr-c777-76hp / CVE-2025-59288 (high): browsers were downloaded without verifying the SSL certificate, fixed in 1.55.1. The advisory had been parked in
npmAuditIgnoreAdvisoriesprecisely because the upgrade could not ride along inside an unrelated change; that entry goes away with it.1.62.1 rather than the minimal 1.55.1: the screenshot cost is identical either way, since any release past 1.55.0 bumps the bundled Chromium and the baselines are compared with
threshold: 0. Taking the latest buys seven minor releases for the same single regeneration.Bundled Chromium moves from 140.0.7339.16 to 151.0.7922.34, so all 215 committed screenshots are regenerated in this pull request via /approve-snapshots.
None of the APIs removed between 1.56 and 1.62 are used here: the suite only touches
test,expect,Page,Locator,page.evaluateandtoHaveScreenshot. Verified locally against Chromium 151 and WebKit 26.5 — every failure is a screenshot mismatch (expected: the baselines are Linux), with no behavioural regression. In particular the clipboard round-trip in textarea still works under the headless clipboard isolation introduced in 1.62.