Skip to content

chore(deps): bump the tests group across 1 directory with 5 updates - #2718

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/tests-711da55770
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/tests-711da55770

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 9, 2026

Copy link
Copy Markdown
Contributor

Bumps the tests group with 5 updates in the / directory:

Package From To
@faker-js/faker 10.5.0 10.6.0
@playwright/test 1.62.1 1.63.0
@vitest/coverage-v8 4.1.10 5.0.0
happy-dom 20.11.1 20.14.5
vitest 4.1.10 5.0.0

Updates @faker-js/faker from 10.5.0 to 10.6.0

Release notes

Sourced from @​faker-js/faker's releases.

v10.6.0

What's Changed

... (truncated)

Changelog

Sourced from @​faker-js/faker's changelog.

10.6.0 (2026-08-14)

New Locales

  • locale: add 060 Japanese mobile phone number formats (#3922) (afa272d)
  • locale: add Norwegian (nb_NO) animal module (#3901) (1232937)
  • locale: add Norwegian (nb_NO) food module (#3900) (bd23594)
  • locale: add vehicle data for de (#3958) (974490f)
  • locale: better middle names by gender for en locale (#3932) (aba3fb1)
  • locale: better organize first_name by gender for en (#3924) (119386b)

Features

Changed Locales

Bug Fixes

  • apidocs: scope code group tab identifiers (#3976) (3125eaf)
  • color: give the LCH hue its full 360 degree range (#3978) (1ce5994)
  • color: stop scaling the HSLA alpha into a percentage (#3979) (1143329)
  • groupBy handling for prototype property keys (#3906) (c898ff1)
  • internet: exclude reserved port 0 from internet.port() (#3948) (d4b35a4)
  • internet: generate long passwords without stack overflow (#3946) (4782978)
  • internet: validate CIDR prefix length and octet range in ipv4() (#3933) (15cb8fb)
  • locale: exclude forbidden letter combinations from nl postcodes (#3888) (9bebe67)
  • locale: only generate valid French postal codes (#3905) (711f36f)
  • locale: update nl_BE phone number patterns (#3981) (9616076)
  • locale: use only common surnames for zh_CN last names (#3938) (58394eb)
  • locale: use only valid letters in en_CA postcodes (#3951) (3b184d6)
  • string: reject refDates that a ULID timestamp cannot encode (#3982) (81717bc)
  • vehicle: calculate VIN check digit (#3954) (a4c6757)
  • word: pick nearest length for closest strategy (#3943) (42fd322)
Commits
  • 2cb0423 chore(release): 10.6.0 (#3986)
  • 531588f chore(deps): lock file maintenance (#3923)
  • 328f018 chore(deps): update eslint (#3930)
  • a5c8bd7 chore(deps): update mcr.microsoft.com/devcontainers/typescript-node:24 docker...
  • fe3f17b chore(deps): update all non-major dependencies (#3974)
  • ae38b18 docs(lorem): document the fail default strategy for word (#3944)
  • 1ce5994 fix(color): give the LCH hue its full 360 degree range (#3978)
  • 1143329 fix(color): stop scaling the HSLA alpha into a percentage (#3979)
  • a4c6757 fix(vehicle): calculate VIN check digit (#3954)
  • d68f978 infra: ensure markdown rendered is only ever initialized once (#3984)
  • Additional commits viewable in compare view

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.10 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 happy-dom from 20.11.1 to 20.14.5

Release notes

Sourced from happy-dom's releases.

v20.14.5

👷‍♂️ Patch fixes

v20.14.4

👷‍♂️ Patch fixes

  • End comments at the first comment end tag when it overlaps a comment start tag - By @​hampustagerud in task #2407

v20.14.3

👷‍♂️ Patch fixes

v20.14.2

👷‍♂️ Patch fixes

  • Fixes regression where not all CSS variables where resolved in getComputedStyle() - By @​klaesra in task #2344

v20.14.1

👷‍♂️ Patch fixes

v20.14.0

🎨 Features

v20.13.2

👷‍♂️ Patch fixes

  • Fix problem with getComputedStyle with :host and :host-context selectors - By @​capricorn86 in task #2349

v20.13.1

👷‍♂️ Patch fixes

  • GetComputedStyle should return inherited value when it is set to inherit - By @​capricorn86 in task #2347

v20.13.0

🎨 Features

v20.12.2

👷‍♂️ Patch fixes

v20.12.1

🎨 Features

  • Adds support for kebab-case properties on CSSStyleDeclaration - By @​capricorn86 in task #2256
  • Adds support for all Chromium CSS properties to CSSStyleDeclaration - By @​capricorn86 in task #2256
    • Downloads a list from the Chromium project when compiling

👷‍♂️ Patch fixes

v20.12.0

... (truncated)

Commits
  • 0d4cdbe fix: #2409 Preserve character references in comment data (#2410)
  • 9c920a4 fix: #2407 End comments at the first comment end tag when it overlaps a com...
  • 5fb1df3 fix: #2363 Avoids cloning all properties in CSSPropertyManager.toString() (...
  • de0a1e9 fix: #2344 Resolve every var() in a value, not only the first one (#2395)
  • 64b8b94 fix: #2366 Invalidate the computed style cache for the whole subtree (#2367)
  • eac5a38 feat: #2357 Improves computed style cache (#2358)
  • 5b3559b fix: #2349 Fix problem with getComputedStyle with :host and :host-context s...
  • f33da73 fix: #2347 getComputedStyle should return inherited value when it is set to...
  • 68b9806 feat: #2345 Adds support for :host psuedo query selector (#2346)
  • 9300a9f fix: #2342 Custom elements should be upgraded when connected to DOM (#2343)
  • Additional commits viewable in compare view

Updates vitest from 4.1.10 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

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Sep 9, 2026
@vercel

vercel Bot commented Sep 9, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated
frontends-starter-template-extended Ready Ready Preview Sep 16, 2026 3:13pm UTC
frontends-vue-starter-template Ready Ready Preview Sep 16, 2026 3:13pm UTC

Request Review

@cursor cursor 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.

Stale comment

Security review

No medium, high, or critical vulnerabilities introduced by this change.

Dependabot tests-group bump only (package.json + lockfile): @faker-js/faker 10.5.0→10.6.0, @playwright/test 1.62.1→1.63.0, vitest / @vitest/coverage-v8 4.1.10→5.0.0, happy-dom 20.11.1→20.14.0. No application source changes. Lockfile integrity hashes match npm for the bumped packages.

These stay in test/e2e tooling (not storefront runtime). Known advisories for older versions (including GHSA-82fw-gwwq-j7x9 on vitest <4.1.11) are patched by the declared versions, not newly introduced. No prior automation security threads to re-validate.

Open in Web View Automation 

Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge

@cursor cursor 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.

Stale comment

Security review

No medium, high, or critical vulnerabilities introduced by this change.

Re-reviewed after Dependabot rebase (ea17402f). Still a tests-group bump only (package.json + lockfile): @faker-js/faker 10.5.0→10.6.0, @playwright/test 1.62.1→1.63.0, vitest / @vitest/coverage-v8 4.1.10→5.0.0, happy-dom 20.11.1→20.14.0. No application source changes. Lockfile integrity hashes match npm for the bumped packages (including playwright, playwright-core, and @vitest/mocker 5.0.0).

These stay in test/e2e tooling (not storefront runtime). @vitest/browser is an optional peer only and is not installed. Known advisories for older versions are patched by the declared versions, not newly introduced: GHSA-82fw-gwwq-j7x9 / CVE-2026-84373 (vitest / @vitest/mocker <4.1.11 and 5.0.0-beta), happy-dom CVE-2026-33943 / CVE-2026-34226 (fixed in 20.8.8 / 20.8.9), faker GHSA-qxc2-j82w-r537 (fixed in 10.5.0). No @playwright/test advisories.

No prior automation security finding threads to re-validate.

Open in Web View Automation 

Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge

@cursor cursor 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.

Stale comment

Security review

No medium, high, or critical vulnerabilities introduced by this change.

Re-reviewed after Dependabot recreate (f79eb76d). Still a tests-group bump only (package.json + lockfile): @faker-js/faker 10.5.0→10.6.0, @playwright/test 1.62.1→1.63.0, vitest / @vitest/coverage-v8 4.1.10→5.0.0, happy-dom 20.11.1→20.14.0. No application source changes. Lockfile integrity hashes match npm for the bumped packages (including playwright, playwright-core, and @vitest/mocker 5.0.0).

These stay in test/e2e tooling (not storefront runtime). @vitest/browser is an optional peer only and is not installed. Known advisories for older versions are patched by the declared versions, not newly introduced: GHSA-82fw-gwwq-j7x9 / CVE-2026-84373 (vitest / @vitest/mocker <4.1.11 and 5.0.0-beta), happy-dom CVE-2026-33943 / CVE-2026-34226 (fixed in 20.8.8 / 20.8.9), faker GHSA-qxc2-j82w-r537 (fixed in 10.5.0). No @playwright/test advisories.

No prior automation security finding threads to re-validate.

Open in Web View Automation 

Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge

Bumps the tests group with 5 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@faker-js/faker](https://github.com/faker-js/faker) | `10.5.0` | `10.6.0` |
| [@playwright/test](https://github.com/microsoft/playwright) | `1.62.1` | `1.63.0` |
| [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) | `4.1.10` | `5.0.0` |
| [happy-dom](https://github.com/capricorn86/happy-dom) | `20.11.1` | `20.14.5` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.10` | `5.0.0` |



Updates `@faker-js/faker` from 10.5.0 to 10.6.0
- [Release notes](https://github.com/faker-js/faker/releases)
- [Changelog](https://github.com/faker-js/faker/blob/next/CHANGELOG.md)
- [Commits](faker-js/faker@v10.5.0...v10.6.0)

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.10 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 `happy-dom` from 20.11.1 to 20.14.5
- [Release notes](https://github.com/capricorn86/happy-dom/releases)
- [Commits](capricorn86/happy-dom@v20.11.1...v20.14.5)

Updates `vitest` from 4.1.10 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: "@faker-js/faker"
  dependency-version: 10.6.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: tests
- dependency-name: "@playwright/test"
  dependency-version: 1.63.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: tests
- dependency-name: "@vitest/coverage-v8"
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: tests
- dependency-name: happy-dom
  dependency-version: 20.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: tests
- dependency-name: vitest
  dependency-version: 5.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: tests
...

Signed-off-by: dependabot[bot] <support@github.com>

@cursor cursor 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.

Security review

No medium, high, or critical vulnerabilities introduced by this change.

Re-reviewed after Dependabot synchronize (4e5478a4). Still a tests-group bump only (package.json + lockfile): @faker-js/faker 10.5.0→10.6.0, @playwright/test 1.62.1→1.63.0, vitest / @vitest/coverage-v8 4.1.10→5.0.0, happy-dom 20.11.1→20.14.5. No application source changes. Lockfile integrity hashes match npm for the bumped packages (including playwright, playwright-core, and @vitest/mocker 5.0.0).

These stay in test/e2e tooling (not storefront runtime). @vitest/browser is an optional peer only and is not installed. Known advisories for older versions are patched by the declared versions, not newly introduced: GHSA-82fw-gwwq-j7x9 / CVE-2026-84373 (vitest / @vitest/mocker <4.1.11 and 5.0.0-beta), happy-dom CVE-2026-33943 / CVE-2026-34226 (fixed in 20.8.8 / 20.8.9), faker GHSA-qxc2-j82w-r537 (fixed in 10.5.0). Browser-mode CVEs (GHSA-g8mr-85jm-7xhm, GHSA-p63j-vcc4-9vmv) are not reachable. No @playwright/test advisories.

No prior automation security finding threads to re-validate.

Open in Web View Automation 

Sent by Cursor Automation: Review pull requests for exploitable security issues and flag only validated findings before merge

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants