Bump @vitest/coverage-v8 from 3.2.4 to 4.0.17#248
Bump @vitest/coverage-v8 from 3.2.4 to 4.0.17#248dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.0.17. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.17/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.17 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dependency version update package.json |
Updated @vitest/coverage-v8 from ^3.2.4 to ^4.0.17 (major version bump) |
Estimated code review effort
🎯 2 (Simple) | ⏱️ ~10 minutes
🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description lacks the required 'Changes' section and is missing the checklist items (labels, documentation, and test updates) specified in the repository template. | Add a 'Changes' section describing the update, and complete the checklist by selecting appropriate labels and confirming documentation/test status. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title accurately describes the main change: updating @vitest/coverage-v8 from version 3.2.4 to 4.0.17 in package.json. |
| Docstring Coverage | ✅ Passed | No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. |
✏️ Tip: You can configure your own custom pre-merge checks in the settings.
Comment @coderabbitai help to get the list of available commands and usage tips.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In @package.json:
- Line 52: package.json has a peer version mismatch: "@vitest/coverage-v8" is
^4.0.17 while "vitest" is ^3.2.4; update the dependency pair so they match.
Either bump "vitest" to a v4.x range (e.g., ^4.0.17) to match
"@vitest/coverage-v8", or replace/downgrade "@vitest/coverage-v8" to a v3.x
compatible version so both vitest and the coverage plugin share the same major
version; adjust the package.json entries for "vitest" and/or
"@vitest/coverage-v8" accordingly and run install to verify no peer dependency
warnings.
📜 Review details
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Disabled knowledge base sources:
- Jira integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (1)
package.json
| "@types/node": "^25.0.2", | ||
| "@types/tmp": "^0.2.6", | ||
| "@vitest/coverage-v8": "^3.2.4", | ||
| "@vitest/coverage-v8": "^4.0.17", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# First, check if package.json exists and show the current vitest versions
echo "=== Current package.json state ==="
if [ -f package.json ]; then
echo "vitest version:"
rg '"vitest"' package.json
echo -e "\n@vitest/coverage-v8 version:"
rg '@vitest/coverage-v8' package.json
else
echo "package.json not found"
fi
# Check peer dependencies for @vitest/coverage-v8 v4.0.17
echo -e "\n=== Checking @vitest/coverage-v8 v4.0.17 peer dependencies ==="
curl -s https://registry.npmjs.org/@vitest/coverage-v8/4.0.17 | jq '.peerDependencies // .peerDependenciesMeta // "No peer dependencies found"'
# Check peer dependencies for @vitest/coverage-v8 v3.2.4
echo -e "\n=== Checking @vitest/coverage-v8 v3.2.4 peer dependencies ==="
curl -s https://registry.npmjs.org/@vitest/coverage-v8/3.2.4 | jq '.peerDependencies // "No peer dependencies found"'Repository: lokalise/node-core
Length of output: 475
Version mismatch between vitest and @vitest/coverage-v8.
The @vitest/coverage-v8 package (v4.0.17) requires vitest v4.0.17 as a peer dependency, but the current vitest version is ^3.2.4 (line 58). This mismatch will cause unmet peer dependency warnings and runtime errors when running coverage.
Update vitest to v4.x to match the coverage plugin:
- "vitest": "^3.2.4",
+ "vitest": "^4.0.17",Or keep both packages at v3:
- "@vitest/coverage-v8": "^4.0.17",
+ "@vitest/coverage-v8": "^3.2.4",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| "@vitest/coverage-v8": "^4.0.17", | |
| "@vitest/coverage-v8": "^3.2.4", |
🤖 Prompt for AI Agents
In @package.json at line 52, package.json has a peer version mismatch:
"@vitest/coverage-v8" is ^4.0.17 while "vitest" is ^3.2.4; update the dependency
pair so they match. Either bump "vitest" to a v4.x range (e.g., ^4.0.17) to
match "@vitest/coverage-v8", or replace/downgrade "@vitest/coverage-v8" to a
v3.x compatible version so both vitest and the coverage plugin share the same
major version; adjust the package.json entries for "vitest" and/or
"@vitest/coverage-v8" accordingly and run install to verify no peer dependency
warnings.
|
Superseded by #254. |
Bumps @vitest/coverage-v8 from 3.2.4 to 4.0.17.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
dd54e94chore: release v4.0.1729ee7f5chore(deps): updateast-v8-to-istanbul(#9418)b094053fix(coverage): remove unnecessaryistanbul-lib-source-mapsusage (#9344)b46d744chore: release v4.0.16eb1abf0chore: release v4.0.159ca74cfchore: release v4.0.14acc5152perf: replacedebugwithobug(#9057)73b54cechore: release v4.0.135aa84d5chore: release v4.0.12c3befb0chore: release v4.0.11Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for
@vitest/coverage-v8since 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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.