Skip to content

build(deps-dev): bump the dev-tooling group across 1 directory with 3 updates - #749

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-tooling-c9c26bdfd5
Open

build(deps-dev): bump the dev-tooling group across 1 directory with 3 updates#749
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-tooling-c9c26bdfd5

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the dev-tooling group with 3 updates in the / directory: @playwright/test, @vitest/coverage-v8 and vitest.

Updates @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

Updates @vitest/coverage-v8 from 4.1.11 to 5.0.0

Release notes

Sourced from @​vitest/coverage-v8's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits

Updates vitest from 4.1.11 to 5.0.0

Release notes

Sourced from vitest's releases.

v5.0.0

Vitest 5 is officially out! This release focuses on performance and brings a lot of new features while fixing long-standing bugs. See our blog post for the official announcement.

   🚨 Breaking Changes

... (truncated)

Commits
  • f441c6f chore: release v5.0.0 (#11130)
  • d46a747 fix: treat test.describe as a suite during static collection (#11128)
  • 584cf30 fix: add a warning if inline project has duplicate plugins due to unexpected ...
  • f08ce4b fix: apply queued mocks from doMock() in queue order (fixes #10706) (#11127)
  • 897f51f chore: release v5.0.0-rc.4 (#11107)
  • 1339b06 chore(deps): update all non-major dependencies (#11104)
  • 51e9494 feat!: parse files statically in vitest list by default (#11088)
  • 2122ffd fix: propagate --maxWorkers to projects (#11102)
  • dc10f5f fix(browser): report the action error when a task times out (#11101)
  • d4fe198 feat: promote clearCache out of experimental (#11086)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 14, 2026
@dependabot
dependabot Bot requested a review from qnbs as a code owner September 14, 2026 23:47
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Sep 14, 2026
@vercel

vercel Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
worldscript-studio Ready Ready Preview Sep 15, 2026 5:06pm UTC

@dependabot dependabot Bot added the javascript Pull requests that update javascript code label Sep 14, 2026
@codeant-ai

codeant-ai Bot commented Sep 14, 2026

Copy link
Copy Markdown

Skipping PR review because a bot author is detected.

If you want to trigger CodeAnt AI, comment @codeant-ai review to trigger a manual review.

@coderabbitai

coderabbitai Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: e77df7bd-9cbc-40f4-b5ca-e63dd41a88cb

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@socket-security

socket-security Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Updatednpm/​@​vitest/​coverage-v8@​4.1.11 ⏵ 5.0.09910079 +198 -1100
Updatednpm/​vitest@​4.1.11 ⏵ 5.0.098 +110079 +198100
Updatednpm/​@​playwright/​test@​1.62.1 ⏵ 1.63.010010010099100

View full report

codescene-access[bot]

This comment was marked as outdated.

Sign in to view

@codecov

codecov Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@codeant-ai

codeant-ai Bot commented Sep 14, 2026 •
edited
Loading

Copy link
Copy Markdown

🏁 CodeAnt Quality Gate Results

Commit: ad8b98a9
Scan Time: 2026-09-15 17:04:58 UTC

✅ Overall Status: PASSED

Quality Gate Details

Quality Gate Status Details
Secrets ✅ PASSED 0 secrets found, 9 false positive secrets suppressed
Duplicate Code ✅ PASSED 0.0% duplicated
SAST ✅ PASSED No security issues
Bugs ✅ PASSED Rating S: No bugs
IAC ✅ PASSED Rating S: No issues

View Full Results

@qnbs

qnbs commented Sep 15, 2026

Copy link
Copy Markdown
Owner

Triage: this group bumps vitest and @vitest/coverage-v8 from 4.1.11 to 5.0.0 — a major version of this repo's core test runner, grouped with a minor @playwright/test bump. CI is genuinely failing (Quality Gate Node 22 and Node 24 both FAILURE, not just pending), consistent with this repo's Dependabot triage policy (docs/DEPENDABOT-TRIAGE.md): major bumps get full manual review and are typically held for a dedicated PR with its own test plan, not merged inline during routine triage. Leaving this open, unmerged, for a dedicated vitest 5 migration PR — not attempting a same-PR fix here since the config/API surface a vitest major usually touches (globals, coverage provider options, workspace config) needs its own scoped investigation.

@dependabot
build(deps-dev): bump the dev-tooling group across 1 directory with 3…
ad8b98a 
… updates

Bumps the dev-tooling group with 3 updates in the / directory: [@playwright/test](https://github.com/microsoft/playwright), [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) and [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest).


Updates `@playwright/test` from 1.62.1 to 1.63.0
- [Release notes](https://github.com/microsoft/playwright/releases)
- [Commits](microsoft/playwright@v1.62.1...v1.63.0)

Updates `@vitest/coverage-v8` from 4.1.11 to 5.0.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/coverage-v8)

Updates `vitest` from 4.1.11 to 5.0.0
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v5.0.0/packages/vitest)

---
updated-dependencies:
- dependency-name: "@playwright/test"
  dependency-version: 1.63.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-tooling
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-tooling
- dependency-name: vitest
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: dev-tooling
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title build(deps-dev): bump the dev-tooling group with 3 updates build(deps-dev): bump the dev-tooling group across 1 directory with 3 updates Sep 15, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/dev-tooling-c9c26bdfd5 branch from 2fe4f2a to ad8b98a Compare September 15, 2026 17:02
codescene-access[bot]
codescene-access Bot approved these changes Sep 15, 2026
View reviewed changes

@codescene-access codescene-access Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No application code in the PR — skipped Code Health checks.

See analysis details in CodeScene

Quality Gate Profile: The Bare Minimum
Install CodeScene MCP: safeguard and uplift AI-generated code. Catch issues early with our IDE extension and CLI tool.

This was referenced Sep 15, 2026
Open
Open
Open
@qnbs ChatGPT Codex Connector

qnbs commented Sep 15, 2026 •
edited
Loading

Copy link
Copy Markdown
Owner

Current disposition — supersede this mixed migration; do not merge as-is — 2026-09-16

Live revalidation of current head ad8b98a9bf8b975f3ed8b96cfdd4733c5177397b confirms this PR is not a routine dependency update:

  • CI/CD run #3190: FAILURE;
  • Node 22 Quality Gate: fails at Typecheck (tsgo);
  • Node 24 Quality Gate: fails at Typecheck (tsgo);
  • unit/build/E2E downstream work is consequently skipped;
  • PR is currently conflicting with newer main;
  • Dependabot metadata bundles Playwright minor with Vitest/coverage major 4→5.

The failure is now classified further: #767 owns the dedicated Vitest 4→5 migration. Current #749 typecheck evidence includes the removed/changed benchmark API (bench no longer exported from vitest) and repository-wide loss of the existing Jest-DOM matcher type augmentation under Vitest 5. This is a real breaking migration, not a lockfile-only update.

Durable ownership is now explicit:

Disposition: do not repair/rebase/merge #749 as one mixed unit. Once #765's grouping policy is corrected, close/supersede this PR and let compatible routine updates regenerate; implement Vitest 5 from a fresh verified main under #767 and handle Playwright under #571.

Do not use @dependabot recreate under the unchanged grouping configuration, because it can reproduce the same mixed-major shape.

This was referenced Sep 15, 2026
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@qnbs qnbs Awaiting requested review from qnbs qnbs is a code owner
1 more reviewer
@codescene-access codescene-access[bot] codescene-access[bot] approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@qnbs