Bump @vitest/coverage-v8 from 4.0.9 to 4.0.13

[dependabot]

Bumps @vitest/coverage-v8 from 4.0.9 to 4.0.13.

Release notes

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

v4.0.13

   🐞 Bug Fixes

• types:
  • Don't use type from Vite 7.1  -  by @​sheremet-va in vitest-dev/vitest#9071 (6356b)
  • Don't import node.js dependent types in vitest/browser  -  by @​sheremet-va in vitest-dev/vitest#9068 (332af)

   🏎 Performance

• Avoid fetchModule roundtrip if the module is cached  -  by @​sheremet-va in vitest-dev/vitest#9075 (b27e0)
• experimental: If fsCacheModule is enabled, read from the memory when possible  -  by @​sheremet-va in vitest-dev/vitest#9076 (6b9a1)

    View changes on GitHub

v4.0.12

   🐞 Bug Fixes

• Inherit fsModuleCachePath by default  -  by @​sheremet-va in vitest-dev/vitest#9063 (9a8bc)
• Don't import from @opentelemetry/api in public types  -  by @​sheremet-va in vitest-dev/vitest#9066 (e944a)

    View changes on GitHub

v4.0.11

   🚀 Experimental Features

• api: Add extensible test artifact API  -  by @​macarie in vitest-dev/vitest#8987 (77292)
  • See more at https://vitest.dev/api/advanced/artifacts
• expect: Provide task in MatchState  -  by @​macarie in vitest-dev/vitest#9022 (afd1f)
• experimental: Support OpenTelemetry traces  -  by @​sheremet-va in vitest-dev/vitest#8994 (d6d33)
  • See more at https://vitest.dev/guide/open-telemetry

   🏎 Performance

• experimental: Add file system cache  -  by @​sheremet-va in vitest-dev/vitest#9026 (1b147)
  • See more at https://vitest.dev/config/experimental#experimental-fsmodulecache

    View changes on GitHub

v4.0.10

   🐞 Bug Fixes

• Remove onCancel when worker is terminated  -  by @​sheremet-va in vitest-dev/vitest#9033 (6d7f0)
• browser:
  • Don't scale the iframe if UI is disabled  -  by @​sheremet-va in vitest-dev/vitest#9018 (5406e)
  • Handle dependency stack traces with external source maps. Resolves: #9003  -  by @​iclectic in vitest-dev/vitest#9016 and vitest-dev/vitest#9003 (57ae5)
• bun:
  • Parsing of stack trace for bun runtime  -  by @​nazarhussain in vitest-dev/vitest#9032 (f3ec6)
• core:
  • Prevent starting new run when cancelling  -  by @​AriPerkkio in vitest-dev/vitest#8991 (eb98d)
• pool:

... (truncated)

Commits

• 73b54ce chore: release v4.0.13
• 5aa84d5 chore: release v4.0.12
• c3befb0 chore: release v4.0.11
• 259a3d1 chore: release v4.0.10
• 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 will merge this PR once CI passes on it, as requested by @guibranco.

---

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[dependabot]

Labels

The following labels could not be found: dependencies, npm. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[semanticdiff-com]

Review changes with  

Changed Files

File	Status
package-lock.json	28% smaller
package.json	0% smaller

[pr-code-reviewer]

👋 Hi there!

Everything looks good!

_{^{Automatically generated with the help of gpt-3.5-turbo.
Feedback? Please don't hesitate to drop me an email at [email protected].}}

[coderabbitai]

Important

Review skipped

Bot user detected.

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

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

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[guibranco]

Automatically approved by gstraccini[bot]

[guibranco]

@dependabot squash and merge

[dependabot]

Beginning January 27, 2026, Dependabot will no longer support the @dependabot squash and merge command. Please use GitHub's native pull request controls instead. Please see the changelog announcement for additional details.

[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/​coverage-v8@​4.0.9 ⏵ 4.0.13				+1
	vitest@​4.0.9 ⏵ 4.0.13	+1		+1	+1

View full report

[dependabot]

One of your CI runs failed on this pull request, so Dependabot won't merge it.

Dependabot will still automatically merge this pull request if you amend it and your tests pass.

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

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Dynamic code execution: npm @vitest/snapshot Eval Type: Function Location: Package overview From: package-lock.json → npm/[email protected] → npm/@vitest/[email protected] ℹ Read more on: This package | This alert | What is dynamic code execution? 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 [email protected]. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/[email protected]. 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		Embedded URLs or IPs: npm @vitest/expect URLs: http://underscorejs.org, https://nodejs.org/docs/latest-v22.x/api/assert.html#comparison-details, https://github.com/facebook/immutable-js, https://github.com/chaijs/loupe/blob/9b8a6deabcd50adc056a64fb705896194710c5c6/src/index.ts#L29, https://github.com/microsoft/TypeScript/issues/61068, Object.is Location: Package overview From: package-lock.json → npm/[email protected] → npm/@vitest/[email protected] ℹ Read more on: This package | This alert | What are URL strings? 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 [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/[email protected]. 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		Embedded URLs or IPs: npm @vitest/runner URLs: https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal, https://vitest.dev/guide/test-context#signal, https://vitest.dev/guide/test-context#ontestfailed, https://vitest.dev/guide/test-context#ontestfinished, https://vitest.dev/guide/test-context#skip, https://vitest.dev/guide/test-context#annotate, https://github.com/unocss/unocss/blob/2e74b31625bbe3b9c8351570749aa2d3f799d919/packages/autocomplete/src/parse.ts#L11, https://github.com/vitest-dev/vitest/pull/7069, vitest.test.id, vitest.test.name, vitest.suite.id, vitest.suite.name, https://vitest.dev/advanced/runner#your-task-function Location: Package overview From: package-lock.json → npm/[email protected] → npm/@vitest/[email protected] ℹ Read more on: This package | This alert | What are URL strings? 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 [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@vitest/[email protected]. 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		Embedded URLs or IPs: npm vitest URLs: 127.0.0.0, https://nodejs.org/docs/latest-v20.x/api/esm.html#resolution-algorithm, https://github.com/nodejs/node/pull/49038, 0.0.0.0, process.env.CI, https://vitest.dev/config/#coverage-reporter, https://github.com/istanbuljs/nyc#coverage-thresholds, https://github.com/istanbuljs/nyc#ignoring-methods, https://vitest.dev/guide/coverage#custom-coverage-provider, https://vitest.dev/config/browser/provider, https://en.wikipedia.org/wiki/Random_seed, https://vitest.dev/config/#sequence-hooks, 127.0.0.1:9229, vitest.runtime.run, vitest.worker.id, task.name, https://vitest.dev/guide/coverage.html#including-and-excluding-files-from-coverage-report, https://istanbul.js.org/docs/advanced/alternative-reporters/, https://trace.playwright.dev/, https://vitest.dev/api/browser/commands, https://vitest.dev/config/#onunhandlederror, https://vitest.dev/config/#root, https://vitest.dev/api/#test, https://nodejs.org/docs/latest/api/cli.html, https://github.com/nodejs/node/issues/41103, https://github.com/chaijs/chai/blob/4.x.x/lib/chai/config.js, https://vitest.dev/guide/open-telemetry, https://github.com/vitest-dev/vitest/issues, https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-error-message, https://github.com/actions/toolkit/blob/f1d9b4b985e6f0f728b4b766db73498403fd5ca3/packages/core/src/command.ts#L80-L85, https://gist.github.com/john-doherty/b9195065884cdbfd2017a4756e6409cc, https://nodejs.org/api/modules.html#built-in-modules-with-mandatory-node-prefix, vitest.module.id, vitest.mock.id, https://vitest.dev/api/vi#vi-advancetimersbytime, https://vitest.dev/api/vi#vi-fn, https://vitest.dev/api/mock, performance.now, Date.now, https://vitest.dev/api/vi#vi-waitfor, https://vitest.dev/api/vi#vi-mock, https://github.com/vitejs/vite/pull/20449, https://github.com/nodejs/node/blob/7c3dce0/lib/internal/modules/package_json_reader.js, browser.name, https://www.cl.cam.ac.uk/%7Emgk25/ucs/utf8_check.c, https://tools.ietf.org/html/rfc6455#section-9.1, https://html.spec.whatwg.org/multipage/comms.html#the-websocket-interface, https://github.com/websockets/ws/issues/1869., https://github.com/websockets/ws/issues/1940., https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Regular_Expressions#escaping, https://github.com/vitest-dev/vitest/pull/7531, vitest.fetched_module.id, https://github.com/vitejs/vite/issues/15438,, https://nodejs.org/api/process.html#signal-events, https://github.com/vitest-dev/vitest/issues/7871, vitest.worker.name, https://github.com/jestjs/jest/blob/25a8785584c9d54a05887001ee7f498d489a5441/packages/jest-worker/src/workers/ChildProcessWorker.ts#L463-L477, https://github.com/tinylibs/tinypool/blob/40b4b3eb926dabfbfd3d0a7e3d1222d4dd1c0d2d/src/runtime/process-worker.ts#L56, https://github.com/vitejs/vite/blob/af2aa09575229462635b7cbb6d248ca853057ba2/packages/vite/src/node/plugins/resolve.ts#L1056-L1080, https://github.com/vitejs/vite/blob/main/packages/vite/src/node/logger.ts?rgh-link-date=2024-10-16T23%3A29%3A19Z, https://github.com/vitejs/vite/pull/15184, https://github.com/vitejs/vite/pull/20502, https://github.com/unjs/mlly/blob/c5bcca0cda175921344fd6de1bc0c499e73e5dac/src/syntax.ts#L51-L98, https://github.com/vitejs/vite/issues/14328, https://vitest.dev/guide/projects, https://vitest.dev/config/#reporters, builder.io/qwik, https://playwright.dev, https://webdriver.io, builder.io/qwik/optimizer, qwik.dev/core, https://vitest.dev/config/browser/playwright, https://vitest.dev/config/browser/webdriverio, https://github.com/sinonjs/sinon/issues/1852#issuecomment-419622780 Location: Package overview From: package-lock.json → npm/[email protected] ℹ Read more on: This package | This alert | What are URL strings? 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 [email protected]. Suggestion: Review all remote URLs to ensure they are intentional, pointing to trusted sources, and not being used for data exfiltration or loading untrusted code at runtime. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. 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.

View full report

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

Update Required: Your current package installation script is outdated and will no longer receive updates.
Please update to the new installation script which can be found here https://infisical.com/docs/cli/overview#installation debian section

A new release of infisical is available: 0.38.0 -> v0.154.0

To update, run: sudo apt-get update && sudo apt-get install infisical

11:40AM INF scanning for exposed secrets...
11:40AM INF 251 commits scanned.
11:40AM INF scan completed in 245ms
11:40AM INF no leaks found

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud