build(deps-dev): bump @playwright/test from 1.58.2 to 1.59.1

[dependabot]

Bumps @playwright/test from 1.58.2 to 1.59.1.

Release notes

Sourced from @​playwright/test's releases.

v1.59.1

Bug Fixes

• [Windows] Reverted hiding console window when spawning browser processes, which caused regressions including broken codegen, --ui and show commands (#39990)

v1.59.0

🎬 Screencast

New page.screencast API provides a unified interface for capturing page content with:

• Screencast recordings
• Action annotations
• Visual overlays
• Real-time frame capture
• Agentic video receipts

Screencast recording — record video with precise start/stop control, as an alternative to the recordVideo option:

await page.screencast.start({ path: 'video.webm' });
// ... perform actions ...
await page.screencast.stop();

Action annotations — enable built-in visual annotations that highlight interacted elements and display action titles during recording:

await page.screencast.showActions({ position: 'top-right' });

screencast.showActions() accepts position ('top-left', 'top', 'top-right', 'bottom-left', 'bottom', 'bottom-right'), duration (ms per annotation), and fontSize (px). Returns a disposable to stop showing actions.

Action annotations can also be enabled in test fixtures via the video option:

// playwright.config.ts
export default defineConfig({
  use: {
    video: {
      mode: 'on',
      show: {
        actions: { position: 'top-left' },
        test: { position: 'top-right' },
      },
</tr></table> 

... (truncated)

Commits

• d466ac5 chore: mark v1.59.1 (#40005)
• 530e7e5 cherry-pick(#4004): fix(cli): kill-all should kill dashboard
• 9aa216c cherry-pick(#39994): Revert "fix(windows): hide console window when spawning ...
• 01b2b15 cherry-pick(#39980): chore: more release notes fixes
• a5cb6c9 cherry-pick(#39972): chore: expose browser.bind and browser.unbind APIs
• 99a17b5 cherry-pick(#39975): chore: support opening .trace files via .link indirection
• 43607c3 cherry-pick(#39974): chore(webkit): update Safari user-agent version to 26.4
• 62cabe1 cherry-pick(#39969): chore(npm): include all *.md from lib (#39970)
• 0c65a75 cherry-pick(#39968): chore: screencast.showActions api
• f04155b cherry-pick(#39958): chore: release notes for langs v1.59
• Additional commits viewable in compare view

[kylewalke]

@dependabot recreate

[github-actions]

E2E Test Results Summary

Run: 540

No test results found

Searched for **/junit.xml and **/results.json under downloaded test-results/ artifacts.

Specs With No Results

The following specs did not produce test results. This usually means the job crashed before tests ran (e.g. build failure, infra error, dependency download timeout).

• apex-extension-core.spec.ts: Did not run — check the job logs
• apex-goto-definition.spec.ts: Did not run — check the job logs
• apex-hover.spec.ts: Did not run — check the job logs
• apex-lsp-integration.spec.ts: Did not run — check the job logs
• apex-outline.spec.ts: Did not run — check the job logs

Artifacts

View detailed test reports in the Artifacts section.

[github-actions]

E2E Test Results Summary

Run: 543

Test Results

• Passed: 0
• Failed: 0
• Errors: 15
• Total: 15

Passing Rate by File

• apex-extension-core.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-lsp-integration.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-hover.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-goto-definition.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-outline.spec.ts/junit.xml: 0.0% (0/3 passed)

Artifacts

View detailed test reports in the Artifacts section.

Some tests failed

[github-actions]

E2E Test Results Summary

Run: 543

Test Results

• Passed: 0
• Failed: 0
• Errors: 15
• Total: 15

Passing Rate by File

• apex-extension-core.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-lsp-integration.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-hover.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-goto-definition.spec.ts/junit.xml: 0.0% (0/3 passed)
• apex-outline.spec.ts/junit.xml: 0.0% (0/3 passed)

Artifacts

View detailed test reports in the Artifacts section.

Some tests failed

[kylewalke]

Blocked on upstream compatibility

This PR's Web E2E failures are not a transient flake — they're a genuine compatibility regression between Playwright 1.59 and @vscode/test-web@0.0.80.

Root cause

The failing tests time out waiting for .cls-ext-file-icon, which is a DOM class VS Code generates per-file-extension only when files are actually visible in the Explorer tree. Screenshots from every failed run show the [Test Files] workspace folder expanded but the tree empty, with a progressbar still spinning.

The test server logs show the files ARE served (GET /static/mount?readdir 200) and the fs extension activates, but an early console warning appears:

Ignoring the error while validating workspace folder vscode-test-web://mount/ - ENOPRO: No file system provider found

In Playwright 1.58.2 (current main), this race resolves and the tree populates. In Playwright 1.59.1's Chromium 147 (headless shell), the tree stays empty — reproduced locally.

Why this isn't fixable in this PR

• Upstream microsoft/vscode-test-web still pins playwright: ^1.58.2 / @playwright/browser-chromium: ^1.58.2. They haven't validated 1.59 yet.
• Simply increasing test timeouts doesn't help — the tree never populates, not even over minutes.
• An npm override to force @vscode/test-web back to playwright@1.58.2 while the test runner uses 1.59 would partially mask the issue but still requires the npx playwright install CLI to install the matching Chromium, which the bot can't manage cleanly.

Recommendation

Close this PR. Re-open when @vscode/test-web ships a version that bumps its Playwright pin. At that point dependabot will pick up the pair together.

[kylewalke]

Closing — see #361 which adds a dependabot ignore entry for Playwright 1.59.x so this unmergeable bump stops getting reopened. Dependabot will offer the next Playwright version once @vscode/test-web@0.0.80 either bumps its own playwright pin or a new test-web release lands.

[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.