Bump the npm_and_yarn group across 1 directory with 2 updates

Open dependabot[bot] opened this issue 11 months ago • 1 comments

Bumps the npm_and_yarn group with 2 updates in the / directory: vitest and @vitest/coverage-v8.

Updates vitest from 1.3.0 to 1.6.1

Release notes

v1.6.1

This release includes security patches for:

Remote Code Execution when accessing a malicious website while Vitest API server is listening | CVE-2025-24964

   🐞 Bug Fixes

backport vitest-dev/vitest#7317 to v1 - by @hi-ogawa in vitest-dev/vitest#7319

    View changes on GitHub

v1.6.0

   🚀 Features

Support standalone mode - by @sheremet-va in vitest-dev/vitest#5565 (bdce0)

Custom "snapshotEnvironment" option - by @sheremet-va in vitest-dev/vitest#5449 (30f72)

benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in vitest-dev/vitest#5398 (f8d3d)

browser: Allow injecting scripts - by @sheremet-va in vitest-dev/vitest#5656 (21e58)

reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa in vitest-dev/vitest#5659 (2f913)

ui: Sort items by file name - by @btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

Keep order of arguments for .each in custom task collectors - by @sheremet-va in vitest-dev/vitest#5640 (7d57c)

Call resolveId('vitest') after buildStart - by @hi-ogawa in vitest-dev/vitest#5646 (f5faf)

Hash the name of the file when caching - by @sheremet-va in vitest-dev/vitest#5654 (c9e68)

Don't panic on empty files in node_modules - by @sheremet-va (40c29)

Use toJSON for error serialization - by @hi-ogawa in vitest-dev/vitest#5526 (19a21)

coverage:

Exclude *.test-d.* by default - by @MindfulPol in vitest-dev/vitest#5634 (bfe8a)

Apply vite-node's wrapper only to executed files - by @AriPerkkio in vitest-dev/vitest#5642 (c9883)

vm:

Support network imports - by @sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

Improve performance of forks pool - by @sheremet-va in vitest-dev/vitest#5592 (d8304)

Unnecessary rpc call when coverage is disabled - by @AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in vitest-dev/vitest#5608 (48fba)

Backport jest iterable equality within object - by @sukovanej in vitest-dev/vitest#5621 (30e5d)

browser: Support benchmark - by @hi-ogawa in vitest-dev/vitest#5622 (becab)

reporter: Use default error formatter for JUnit - by @hi-ogawa in vitest-dev/vitest#5629 (20060)

... (truncated)

Commits

017e1ee chore: release v1.6.1
7ce9fbb fix: backport #7317 to v1 (#7319)
6b29f3d chore: release v1.6.0
f8d3d22 feat(benchmark): support comparing benchmark result (#5398)
21e58bd feat(browser): allow injecting scripts (#5656)
30f728b feat: custom "snapshotEnvironment" option (#5449)
2f91322 feat(reporter): support includeConsoleOutput and addFileAttribute in juni...
c571276 perf: unnecessary rpc call when coverage is disabled (#5658)
bdce0a2 feat: support standalone mode (#5565)
40c299f fix: don't panic on empty files in node_modules
Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 1.3.0 to 1.6.1

Release notes

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

v1.6.1

This release includes security patches for:

Remote Code Execution when accessing a malicious website while Vitest API server is listening | CVE-2025-24964

   🐞 Bug Fixes

backport vitest-dev/vitest#7317 to v1 - by @hi-ogawa in vitest-dev/vitest#7319

    View changes on GitHub

v1.6.0

   🚀 Features

Support standalone mode - by @sheremet-va in vitest-dev/vitest#5565 (bdce0)

Custom "snapshotEnvironment" option - by @sheremet-va in vitest-dev/vitest#5449 (30f72)

benchmark: Support comparing benchmark result - by @hi-ogawa and @sheremet-va in vitest-dev/vitest#5398 (f8d3d)

browser: Allow injecting scripts - by @sheremet-va in vitest-dev/vitest#5656 (21e58)

reporter: Support includeConsoleOutput and addFileAttribute in junit - by @hi-ogawa in vitest-dev/vitest#5659 (2f913)

ui: Sort items by file name - by @btea in vitest-dev/vitest#5652 (1f726)

   🐞 Bug Fixes

Keep order of arguments for .each in custom task collectors - by @sheremet-va in vitest-dev/vitest#5640 (7d57c)

Call resolveId('vitest') after buildStart - by @hi-ogawa in vitest-dev/vitest#5646 (f5faf)

Hash the name of the file when caching - by @sheremet-va in vitest-dev/vitest#5654 (c9e68)

Don't panic on empty files in node_modules - by @sheremet-va (40c29)

Use toJSON for error serialization - by @hi-ogawa in vitest-dev/vitest#5526 (19a21)

coverage:

Exclude *.test-d.* by default - by @MindfulPol in vitest-dev/vitest#5634 (bfe8a)

Apply vite-node's wrapper only to executed files - by @AriPerkkio in vitest-dev/vitest#5642 (c9883)

vm:

Support network imports - by @sheremet-va in vitest-dev/vitest#5610 (103a6)

   🏎 Performance

Improve performance of forks pool - by @sheremet-va in vitest-dev/vitest#5592 (d8304)

Unnecessary rpc call when coverage is disabled - by @AriPerkkio in vitest-dev/vitest#5658 (c5712)

    View changes on GitHub

v1.5.3

   🐞 Bug Fixes

Use package.json name for a workspace project if not provided - by @sheremet-va in vitest-dev/vitest#5608 (48fba)

Backport jest iterable equality within object - by @sukovanej in vitest-dev/vitest#5621 (30e5d)

browser: Support benchmark - by @hi-ogawa in vitest-dev/vitest#5622 (becab)

reporter: Use default error formatter for JUnit - by @hi-ogawa in vitest-dev/vitest#5629 (20060)

... (truncated)

Commits

017e1ee chore: release v1.6.1
73cb696 docs: show a warning in v1 docs (#7003)
6b29f3d chore: release v1.6.0
c9883f3 fix(coverage): apply vite-node's wrapper only to executed files (#5642)
a52964b chore: release v1.5.3
81f57f4 chore: release v1.5.2
1be4510 chore: release v1.5.1
80265b4 fix(coverage): thresholds to compare files relative to root (#5574)
ea3c16e fix(coverage): prevent crash when cleanOnRerun is disabled (#5540)
9e7a01c chore: release v1.5.0
Additional commits viewable 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 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
@dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
@dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
@dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
@dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page.

Feb 12 '25 02:02 dependabot[bot]

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

Feb 12 '25 02:02 sonarqubecloud[bot]