[dependabot]

Bumps @vitest/mocker to 4.1.12 and updates ancestor dependency vitest. These dependencies need to be updated together.

Updates @vitest/mocker from 4.1.11 to 4.1.12

Release notes

Sourced from @​vitest/mocker's releases.

v4.1.12

   🐞 Bug Fixes

• mocker: Harden manual and redirect mocks [backport to v4]  -  by @​sheremet-va in vitest-dev/vitest#11580 (b8253)

    View changes on GitHub

Commits

• 4766ce1 chore: release v4.1.12 (#11610)
• b825313 fix(mocker): harden manual and redirect mocks [backport to v4] (#11580)
• See full diff in compare view

Updates vitest from 4.1.11 to 4.1.12

Release notes

Sourced from vitest's releases.

v4.1.12

   🐞 Bug Fixes

• mocker: Harden manual and redirect mocks [backport to v4]  -  by @​sheremet-va in vitest-dev/vitest#11580 (b8253)

    View changes on GitHub

Commits

• 4766ce1 chore: release v4.1.12 (#11610)
• 5bf2197 chore: delete wdio folder from v4 branch to avoid falsy release (#11581)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	vitest@​4.1.11 ⏵ 4.1.12

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Priority	Alert  (click "▶" to expand/collapse)	Action
	Recently published: npm @vitest/expect published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/expect@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/expect@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/mocker published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/mocker@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/mocker@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/pretty-format published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/pretty-format@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/pretty-format@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/runner published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/runner@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/runner@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/snapshot published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/snapshot@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/snapshot@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/spy published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/spy@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/spy@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block
	Recently published: npm @vitest/utils published 6 days ago Location: Package overview From: package-lock.json → npm/vitest@4.1.12 → npm/@vitest/utils@4.1.12 ℹ Read more on: This package | This alert | What are recently published artifacts? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should either be allowlisted to allow recently-published versions, or an older version should be used instead. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/utils@4.1.12. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.	Block

View full report

[claude]

LGTM. This is a routine patch bump of the vitest dev dependency.

What was reviewed:

• package.json: the exact pin for vitest moves from 4.1.11 to 4.1.12, so the repo still uses exact devDependency pins.
• package-lock.json: all @ vitest/* packages move to 4.1.12, chai to 6.3.0 and tinyrainbow to 3.2.0. Every resolved URL points at registry.npmjs.org.
• The ^4.1.11 peer range for @ vitest/browser-webdriverio comes from vitest's own published metadata (upstream deleted the wdio package from the v4 branch). It is an optional peer that this repo doesn't install.

Extended reasoning...

The change touches only package.json and package-lock.json, bumping the devDependency vitest and its @ vitest/* subpackages by one patch version, plus minor bumps to the transitive packages chai and tinyrainbow. No source, test or config files change. It touches no security-sensitive code paths. The packages are only used for running tests. All tarballs resolve from the public npm registry. The repository has no CODEOWNERS file, there are no reviewer objections, and the bug hunt ran until it stopped finding anything.

[dependabot]

Looks like these dependencies are up-to-date now, so this is no longer needed.