Conversation
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 3.2.4 to 4.1.0. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 4.1.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
requested review from
a team,
CarlosGamero,
drdaemos and
kibertoad
as code owners
📝 WalkthroughSummary by CodeRabbit
WalkthroughA devDependency version for vitest in package.json is updated from ^3.2.4 to ^4.1.0. This represents a major version upgrade of the testing framework, including all minor and patch releases up to version 4.1.0. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@package.json`:
- Line 86: The package.json currently upgrades vitest to ^4.1.0 but leaves
`@vitest/coverage-v8` at ^3.2.4; update the `@vitest/coverage-v8` devDependency to a
v4-compatible version (e.g. ^4.0.0 or the latest 4.x) so it matches Vitest 4's
peer dependency, then reinstall dependencies (npm/yarn/pnpm) and run your test
coverage command to verify coverage runs; target the "@vitest/coverage-v8" entry
in package.json and ensure the version string is updated to a 4.x range.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 51582b56-4c50-4109-b535-fd3747edfbe8
📒 Files selected for processing (1)
package.json
| "rimraf": "^6.0.1", | ||
| "typescript": "^5.9.3", | ||
| "vitest": "^3.2.4", | ||
| "vitest": "^4.1.0", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
python3 - <<'PY'
import json, urllib.request
def get_pkg(name, version):
url = f"https://registry.npmjs.org/{name}/{version}"
with urllib.request.urlopen(url) as r:
return json.load(r)
cov = get_pkg("@vitest/coverage-v8", "3.2.4")
vit = get_pkg("vitest", "4.1.0")
print("@vitest/coverage-v8@3.2.4 peerDependencies:")
print(json.dumps(cov.get("peerDependencies", {}), indent=2))
print("\nvitest@4.1.0 version:", vit.get("version"))
PYRepository: lokalise/fastify-extras
Length of output: 2685
🏁 Script executed:
cat -n package.json | sed -n '70,90p'Repository: lokalise/fastify-extras
Length of output: 861
🌐 Web query:
vitest 4.1.0 @vitest/coverage-v8 compatibility peer dependencies
💡 Result:
For Vitest 4.1.0, the @vitest/coverage-v8 package you should use is @vitest/coverage-v8@4.1.0, because it declares exact-version peer deps:
@vitest/coverage-v8@4.1.0peerDependencies:vitest:4.1.0@vitest/browser:4.1.0(optional)[1]
So the compatible pairing is:
vitest@4.1.0+@vitest/coverage-v8@4.1.0[1][2]
Install:
npm i -D vitest@4.1.0 `@vitest/coverage-v8`@4.1.0Upgrade @vitest/coverage-v8 to major version 4 to match Vitest 4.
Line 86 upgrades vitest to ^4.1.0, but Line 74 keeps @vitest/coverage-v8 at ^3.2.4. The coverage plugin has exact peer dependency on vitest@4.1.0, making this combination incompatible and breaking coverage runs.
Suggested fix
- "@vitest/coverage-v8": "^3.2.4",
+ "@vitest/coverage-v8": "^4.1.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@package.json` at line 86, The package.json currently upgrades vitest to
^4.1.0 but leaves `@vitest/coverage-v8` at ^3.2.4; update the `@vitest/coverage-v8`
devDependency to a v4-compatible version (e.g. ^4.0.0 or the latest 4.x) so it
matches Vitest 4's peer dependency, then reinstall dependencies (npm/yarn/pnpm)
and run your test coverage command to verify coverage runs; target the
"@vitest/coverage-v8" entry in package.json and ensure the version string is
updated to a 4.x range.
|
Superseded by #383. |
Bumps vitest from 3.2.4 to 4.1.0.
Release notes
Sourced from vitest's releases.
... (truncated)
Commits
4150b91chore: release v4.1.01de0aa2fix: correctly identify concurrent test during static analysis (#9846)c3cac1cfix: use isAgent check, not just TTY, for watch mode (#9841)eab68bachore(deps): update all non-major dependencies (#9824)031f02afix: allow catch/finally for async assertion (#9827)3e9e096feat(reporters): addagentreporter to reduce ai agent token usage (#9779)0c2c013chore: release v4.1.0-beta.68181e06fix:hideSkippedTestsshould not hidetest.todo(fix #9562) (#9781)a8216b0fix: manual and redirect mock shouldn'tloadortransformoriginal module...689a22afix(browser): types ofgetCDPSessionandcdp()(#9716)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for vitest since your current version.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)