[dependabot]

Bumps @playwright/test from 1.62.1 to 1.63.0.

Release notes

Sourced from @​playwright/test's releases.

v1.63.0

🔒 Test locks

Tests that access a shared resource — an external service, a global account setting — can now declare a named lock. Tests that share a lock name never run concurrently, across files, workers and projects, while everything else keeps running in parallel:

test('update user settings', { lock: 'user-settings' }, async ({ page }) => {
  // never runs at the same time as other tests holding 'user-settings'
});

A test can hold multiple locks, and test.describe() accepts a lock for the whole group. Learn more about test locks.

🪟 Locate across frames

page.frameLocator() and frame.frameLocator() called without a selector search in any frame of the subtree, so you no longer need to locate the iframe first:

// Finds the button in any frame on the page.
await page.frameLocator().getByRole('button').click();

The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it matches elements in several frames.

👁️ Visible-only locators

New locator.visible() returns a locator that matches only visible elements. It is the recommended replacement for the :visible CSS pseudo-class:

await page.locator('button').visible().click();

🧾 Step params and subtitles

Steps now carry structured data for reporters. Playwright API steps report the target locator and call arguments, and test.step() accepts subtitle and params options for your own steps:

await test.step('Login', async () => {
  // ...
}, { subtitle: 'as admin', params: { user: 'admin' } });

Reporters receive them via testStep.subtitle and testStep.params. For Playwright API

... (truncated)

Commits

• 1b025d7 chore: mark v1.63.0 (#42569)
• 0b9956d cherry-pick(#42568): docs(test): mark test.step subtitle option as since v1.63
• 13dbf10 cherry-pick(#42552): docs: release notes for v1.63
• e93b64e cherry-pick(#42566): feat(test): add subtitle option to test.step (#42567)
• 2b7a5f2 test: response.body() for content-encoding:identity (#42537)
• 648a67c fix(mcp): create parent directories for explicitly named files (#42540)
• 7894f56 docs(mcp): clarify how tool file names are resolved (#42538)
• 52900a1 devops: restore npm publishing from GitHub Actions (#42550)
• 8c47f59 docs(csharp): fix nonexistent method names in guide examples (#42507)
• bd6e552 chore(video): emit frames with real timestamps, drop frame number quantizatio...
• Additional commits viewable in compare view

[bito-code-review]

Bito Automatic Review Skipped - Files Excluded

Bito didn't auto-review this change because all changed files are in the exclusion list for automatic reviews. No action is needed if you didn't intend for the agent to review it. Otherwise, to manually trigger a review, type /review in a comment and save.
You can change the excluded files settings here, or contact your Bito workspace admin at evan@preset.io.

[netlify]

✅ Deploy Preview for superset-docs-preview ready!

Name	Link
🔨 Latest commit	d8f25d0
🔍 Latest deploy log	https://app.netlify.com/projects/superset-docs-preview/deploys/6ab1dcf475fee90007722247
😎 Deploy Preview	https://deploy-preview-44231--superset-docs-preview.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.28%. Comparing base (2ad0053) to head (b4faa04).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #44231      +/-   ##
==========================================
+ Coverage   76.56%   80.28%   +3.71%     
==========================================
  Files        2932     2931       -1     
  Lines      174527   174264     -263     
  Branches    40546    40506      -40     
==========================================
+ Hits       133628   139904    +6276     
+ Misses      38129    31684    -6445     
+ Partials     2770     2676      -94     

Flag	Coverage Δ
javascript	75.85% <ø> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[rusackas]

Minor Playwright bump, CI green, LGTM.

[rusackas]

@dependabot recreate

[rusackas]

@dependabot recreate

[rusackas]

Not the usual master churn this time (#44513 and #44509 cover the lint and messages.pot reds). The export/zip playwright tests fail on the bump itself: with 1.63.0's Chromium 153, response.body() comes back empty for the fetched export, so expectValidExportZip has nothing to unzip. Parking this until those tests get reworked.

[rusackas]

Traced the playwright-tests failures here. @playwright/test 1.63.0 has a real regression: response.body() on a page-level Response (captured via page.waitForResponse()) comes back empty once the in-page JS has already read the same response via .blob() - which is exactly what handleResourceExport in src/utils/export.ts does to turn the export into a downloadable file. The browser itself gets the file fine (blob.size is correct), it's just Playwright's own body capture that's broken on the Node side, so this is a test-visibility regression, not an app bug.

Bisected and minimal-repro'd, filed upstream: microsoft/playwright#42862.

Holding this until that's fixed upstream.

[rusackas]

Root-caused and fixed upstream: microsoft/playwright#42863. Still needs a maintainer to review/merge there before there's a patched release to bump to.

[sadpandajoe]

Going to close this

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.