Conversation
Snyk has created this PR to upgrade playwright from 1.56.1 to 1.57.0. See this package in npm: playwright See this project in Snyk: https://app.snyk.io/org/ssdeanx/project/97f9b44f-04aa-4c4a-a071-4c3e5cc49f97?utm_source=github&utm_medium=referral&page=upgrade-pr
Learn moreAll Green is an AI agent that automatically: ✅ Addresses code review comments ✅ Fixes failing CI checks ✅ Resolves merge conflicts |
|
Important Review skippedIgnore keyword(s) in the title. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
🤖 Hi @ssdeanx, I've received your request, and I'm working on it now! You can track my progress in the logs for more details. |
Summary of ChangesHello @ssdeanx, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request, automatically generated by Snyk, updates the Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request, automatically generated by Snyk, upgrades the playwright dependency from version 1.56.1 to 1.57.0. This is a minor update, but it includes a significant breaking change: the removal of the deprecated Page#accessibility API. I have reviewed the code changes and the provided files, and I did not find any usage of this API. However, to ensure a safe upgrade, it is crucial to run the full test suite, especially any end-to-end tests, to verify that this change does not introduce any regressions. The version update in package.json is correct.
|
🤖 I'm sorry @ssdeanx, but I was unable to process your request. Please see the logs for more details. |
There was a problem hiding this comment.
Pull request overview
This PR upgrades the Playwright dependency from version 1.56.1 to 1.57.0, an automated update created by Snyk. This is a minor version upgrade released on November 25, 2025 (25 days ago), 61 versions ahead of the current version.
Key changes in Playwright 1.57.0:
- New "Speedboard" feature in HTML reporter for test performance analysis
- Switch from Chromium to Chrome for Testing builds
- Breaking change: Removal of
Page#accessibilityAPI after 3 years of deprecation - New webServer
waitfield for waiting on stdout/stderr output - Service Worker network requests now reported and routable in Chromium
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Updates Playwright version from ^1.56.1 to ^1.57.0 |
| package-lock.json | Updates resolved Playwright and playwright-core versions to 1.57.0; adjusts peer dependency flags for various transitive dependencies as expected when a direct dependency is upgraded |
| "next-themes": "^0.4.6", | ||
| "pdf-parse": "^2.4.5", | ||
| "playwright": "^1.56.1", | ||
| "playwright": "^1.57.0", |
There was a problem hiding this comment.
This upgrade includes a breaking change: the Page#accessibility API has been removed from Playwright after being deprecated for 3 years. If this project or any dependencies use page.accessibility, the code will need to be updated to use alternative accessibility testing libraries like Axe. Before merging, verify that no code in the project uses the page.accessibility API.
| "playwright": "^1.57.0", | |
| "playwright": "1.56.0", |
Snyk has created this PR to upgrade playwright from 1.56.1 to 1.57.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 61 versions ahead of your current version.
The recommended version was released 25 days ago.
Release notes
Package name: playwright
-
1.57.0 - 2025-11-25
import { defineConfig } from '@ playwright/test';
import { test, expect } from '@ playwright/test';
- New property testConfig.tag adds a tag to all tests in this run. This is useful when using merge-reports.
- worker.on('console') event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. worker.waitForEvent() can be used to wait for it.
- locator.description() returns locator description previously set with locator.describe(), and
- New option
- Network requests issued by Service Workers are now reported and can be routed through the BrowserContext, only in Chromium. You can opt out using the
- Console messages from Service Workers are dispatched through worker.on('console'). You can opt out of this using the
- Chromium 143.0.7499.4
- Mozilla Firefox 144.0.2
- WebKit 26.0
-
1.57.0-beta-1765994843000 - 2025-12-17
-
1.57.0-beta-1765994134000 - 2025-12-17
-
1.57.0-beta-1764944708000 - 2025-12-05
-
1.57.0-beta-1764692940000 - 2025-12-02
-
1.57.0-beta-1764069017000 - 2025-11-25
-
1.57.0-beta-1764065820000 - 2025-11-25
-
1.57.0-beta-1763739794000 - 2025-11-21
-
1.57.0-beta-1763718928000 - 2025-11-21
-
1.57.0-beta-1763649092000 - 2025-11-20
-
1.57.0-alpha-2025-11-20 - 2025-11-20
-
1.57.0-alpha-2025-11-19 - 2025-11-19
-
1.57.0-alpha-2025-11-18 - 2025-11-18
-
1.57.0-alpha-2025-11-17 - 2025-11-17
-
1.57.0-alpha-2025-11-16 - 2025-11-16
-
1.57.0-alpha-2025-11-15 - 2025-11-15
-
1.57.0-alpha-2025-11-14 - 2025-11-14
-
1.57.0-alpha-2025-11-13 - 2025-11-13
-
1.57.0-alpha-2025-11-12 - 2025-11-12
-
1.57.0-alpha-2025-11-11 - 2025-11-11
-
1.57.0-alpha-2025-11-10 - 2025-11-10
-
1.57.0-alpha-2025-11-09 - 2025-11-09
-
1.57.0-alpha-2025-11-08 - 2025-11-08
-
1.57.0-alpha-2025-11-07 - 2025-11-07
-
1.57.0-alpha-2025-11-06 - 2025-11-06
-
1.57.0-alpha-2025-11-05 - 2025-11-05
-
1.57.0-alpha-2025-11-04 - 2025-11-04
-
1.57.0-alpha-2025-11-03 - 2025-11-03
-
1.57.0-alpha-2025-11-02 - 2025-11-02
-
1.57.0-alpha-2025-11-01 - 2025-11-01
-
1.57.0-alpha-2025-10-31 - 2025-10-31
-
1.57.0-alpha-2025-10-30 - 2025-10-30
-
1.57.0-alpha-2025-10-29 - 2025-10-29
-
1.57.0-alpha-2025-10-28 - 2025-10-28
-
1.57.0-alpha-2025-10-27 - 2025-10-27
-
1.57.0-alpha-2025-10-26 - 2025-10-26
-
1.57.0-alpha-2025-10-25 - 2025-10-25
-
1.57.0-alpha-2025-10-24 - 2025-10-24
-
1.57.0-alpha-2025-10-23 - 2025-10-23
-
1.57.0-alpha-2025-10-22 - 2025-10-22
-
1.57.0-alpha-2025-10-21 - 2025-10-21
-
1.57.0-alpha-2025-10-20 - 2025-10-20
-
1.57.0-alpha-2025-10-19 - 2025-10-19
-
1.57.0-alpha-2025-10-18 - 2025-10-18
-
1.57.0-alpha-2025-10-17 - 2025-10-17
-
1.57.0-alpha-2025-10-16 - 2025-10-16
-
1.57.0-alpha-2025-10-15 - 2025-10-15
-
1.57.0-alpha-2025-10-14 - 2025-10-14
-
1.57.0-alpha-2025-10-13 - 2025-10-13
-
1.57.0-alpha-2025-10-12 - 2025-10-12
-
1.57.0-alpha-2025-10-11 - 2025-10-11
-
1.57.0-alpha-2025-10-10 - 2025-10-10
-
1.57.0-alpha-2025-10-09 - 2025-10-09
-
1.57.0-alpha-2025-10-08 - 2025-10-08
-
1.57.0-alpha-2025-10-07 - 2025-10-07
-
1.57.0-alpha-2025-10-06 - 2025-10-06
-
1.57.0-alpha-2025-10-05 - 2025-10-05
-
1.57.0-alpha-2025-10-04 - 2025-10-04
-
1.57.0-alpha-2025-10-03 - 2025-10-03
-
1.57.0-alpha-1761929702000 - 2025-10-31
-
1.57.0-alpha-1760728340000 - 2025-10-17
-
1.56.1 - 2025-10-17
- Chromium 141.0.7390.37
- Mozilla Firefox 142.0.1
- WebKit 26.0
from playwright GitHub release notesSpeedboard
In HTML reporter, there's a new tab we call "Speedboard":
It shows you all your executed tests sorted by slowness,
and can help you understand where your test suite is taking longer than expected.
Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!
Chrome for Testing
Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.
We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.
If you still see an unexpected behaviour change, please file an issue.
On Arm64 Linux, Playwright continues to use Chromium.
Waiting for webserver output
testConfig.webServer added a
waitfield. Pass a regular expression, and Playwright will wait until the webserver logs match it.export default defineConfig({
webServer: {
command: 'npm run start',
wait: {
stdout: '/Listening on port (?<my_server_port>\d+)/'
},
},
});
If you include a named capture group into the expression, then Playwright will provide the capture group contents via environment variables:
test.use({ baseUrl:
http://localhost:<span class="pl-s1"><span class="pl-kos">${</span><span class="pl-s1">process</span><span class="pl-kos">.</span><span class="pl-c1">env</span><span class="pl-kos">.</span><span class="pl-c1">MY_SERVER_PORT</span> <span class="pl-c1">??</span> <span class="pl-c1">3000</span><span class="pl-kos">}</span></span>});test('homepage', async ({ page }) => {
await page.goto('/');
});
This is not just useful for capturing varying ports of dev servers. You can also use it to wait for readiness of a service that doesn't expose an HTTP readiness check, but instead prints a readiness message to stdout or stderr.
Breaking Change
After 3 years of being deprecated, we removed
Page#accessibilityfrom our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.New APIs
Locator.toString()now uses the description when available.stepsin locator.click() and locator.dragTo() that configures the number ofmousemoveevents emitted while moving the mouse pointer to the target element.PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORKenvironment variable.PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLEenvironment variable.Browser Versions
Highlights
#37871 chore: allow local-network-access permission in chromium
#37891 fix(agents): remove workspaceFolder ref from vscode mcp
#37759 chore: rename agents to test agents
#37757 chore(mcp): fallback to cwd when resolving test config
Browser Versions
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information: