Update @vitest/coverage-v8 2.1.6 → 2.1.8 (patch)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​vitest/coverage-v8 (2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

✳️ vitest (2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/expect (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/mocker (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/pretty-format (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/runner (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/snapshot (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/spy (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ @​vitest/utils (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

↗️ vite-node (indirect, 2.1.6 → 2.1.8) · Repo

Release Notes

2.1.8

   🐞 Bug Fixes

• Support Node 21  -  by @sheremet-va (92f7a)

    View changes on GitHub

2.1.7

   🐞 Bug Fixes

• Revert support for Vite 6  -  by @sheremet-va (fbe5c)
  • This introduced some breaking changes (#6992). We will enable support for it later. In the meantime, you can still use pnpm.overrides or yarn resolutions to override the vite version in the vitest package - the APIs are compatible.

    View changes on GitHub

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 4 commits:

• bump: 2.1.8
• fix: support Node 21
• chore: release v2.1.7
• fix: revert support for Vite 6

🆕 @​esbuild/aix-ppc64 (added, 0.21.5)

🆕 @​esbuild/android-arm (added, 0.21.5)

🆕 @​esbuild/android-arm64 (added, 0.21.5)

🆕 @​esbuild/android-x64 (added, 0.21.5)

🆕 @​esbuild/darwin-arm64 (added, 0.21.5)

🆕 @​esbuild/darwin-x64 (added, 0.21.5)

🆕 @​esbuild/freebsd-arm64 (added, 0.21.5)

🆕 @​esbuild/freebsd-x64 (added, 0.21.5)

🆕 @​esbuild/linux-arm (added, 0.21.5)

🆕 @​esbuild/linux-arm64 (added, 0.21.5)

🆕 @​esbuild/linux-ia32 (added, 0.21.5)

🆕 @​esbuild/linux-loong64 (added, 0.21.5)

🆕 @​esbuild/linux-mips64el (added, 0.21.5)

🆕 @​esbuild/linux-ppc64 (added, 0.21.5)

🆕 @​esbuild/linux-riscv64 (added, 0.21.5)

🆕 @​esbuild/linux-s390x (added, 0.21.5)

🆕 @​esbuild/linux-x64 (added, 0.21.5)

🆕 @​esbuild/netbsd-x64 (added, 0.21.5)

🆕 @​esbuild/openbsd-x64 (added, 0.21.5)

🆕 @​esbuild/sunos-x64 (added, 0.21.5)

🆕 @​esbuild/win32-arm64 (added, 0.21.5)

🆕 @​esbuild/win32-ia32 (added, 0.21.5)

🆕 @​esbuild/win32-x64 (added, 0.21.5)

🆕 esbuild (added, 0.21.5)

🆕 vite (added, 5.4.11)

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[code-genius-code-coverage]

The files' contents are under analysis for test generation.

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

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[guibranco]

Automatically approved by gstraccini[bot]

[guibranco]

@depfu merge

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/@vitest/[email protected]	Transitive: environment, filesystem, shell	+62	10.3 MB	antfu, oreanno, patak, ...1 more
npm/[email protected]	Transitive: environment, eval, filesystem, network, shell, unsafe	+84	284 MB	antfu, oreanno, patak, ...1 more

🚮 Removed packages: npm/@vitest/[email protected], npm/[email protected]

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Dynamic require	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫
High entropy strings	npm/[email protected]	Location: Package overview	package-lock.json package.json	🚫

View full report↗︎

Next steps

What is dynamic require?

Dynamic require can indicate the package is performing dangerous or unsafe dynamic code execution.

Packages should avoid dynamic imports when possible. Audit the use of dynamic require to ensure it is not executing malicious or vulnerable code.

What are high entropy strings?

Contains high entropy strings. This could be a sign of encrypted data, leaked secrets or obfuscated code.

Please inspect these strings to check if they are benign. Maintainers should clarify the purpose and existence of high entropy strings if there is a legitimate purpose.

Take a deeper look at the dependency

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 [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/[email protected] or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/[email protected]

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

💻 Scan logs

1:18AM INF scanning for exposed secrets...
1:18AM INF 46 commits scanned.
1:18AM INF scan completed in 107ms
1:18AM 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