Bump @vitest/coverage-v8 from 3.2.4 to 4.1.7 - #290
Conversation
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.1.7. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.7/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.1.7 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
📝 WalkthroughSummary by CodeRabbit
WalkthroughThis PR updates the Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@package.json`:
- Line 52: Update package.json devDependencies so Vitest and related `@vitest`
packages use matching 4.1.7 versions: change the vitest entry (currently ^3.2.4)
to 4.1.7 and, if present, change `@vitest/browser` to 4.1.7 to match
`@vitest/coverage-v8`@4.1.7; ensure the devDependencies block consistently
references vitest 4.1.7 and run install to verify no peerDependency warnings.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository: lokalise/coderabbit/.coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 8b8642ec-0460-44e1-8372-60666bb65b54
📒 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.1.7", |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Local package.json versions:"
python - <<'PY'
import json
p=json.load(open("package.json"))
d=p.get("devDependencies",{})
print("`@vitest/coverage-v8` =", d.get("`@vitest/coverage-v8`"))
print("vitest =", d.get("vitest"))
PY
echo
echo "Registry peerDependencies for `@vitest/coverage-v8`@4.1.7:"
npm view `@vitest/coverage-v8`@4.1.7 peerDependencies --jsonRepository: lokalise/node-core
Length of output: 248
Fix Vitest version alignment for @vitest/coverage-v8 (package.json devDependencies, Line 52).
@vitest/coverage-v8@4.1.7 declares peerDependencies on vitest: "4.1.7" (and @vitest/browser: "4.1.7"), but this repo keeps vitest at ^3.2.4 (Line 58). Align vitest to 4.1.7 (and @vitest/browser to 4.1.7 if present) to avoid install/CI and coverage incompatibilities.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@package.json` at line 52, Update package.json devDependencies so Vitest and
related `@vitest` packages use matching 4.1.7 versions: change the vitest entry
(currently ^3.2.4) to 4.1.7 and, if present, change `@vitest/browser` to 4.1.7 to
match `@vitest/coverage-v8`@4.1.7; ensure the devDependencies block consistently
references vitest 4.1.7 and run install to verify no peerDependency warnings.
|
Superseded by #291. |
Bumps @vitest/coverage-v8 from 3.2.4 to 4.1.7.
Release notes
Sourced from @vitest/coverage-v8's releases.
... (truncated)
Commits
a09d472chore: release v4.1.7a8fd24cchore: release v4.1.6e399846chore: release v4.1.5ac04bacchore: release v4.1.42dc0d62chore: release v4.1.3fc6f482chore: release v4.1.21f2d318chore: release v4.1.1aaf9f18fix(coverage): simplify provider types (#9931)4150b91chore: release v4.1.00c2c013chore: release v4.1.0-beta.6Maintainer changes
This version was pushed to npm by 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 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)