Skip to content

Bump @vitest/coverage-v8 from 3.2.4 to 4.1.7 - #290

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.7
Closed

Bump @vitest/coverage-v8 from 3.2.4 to 4.1.7#290
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/vitest/coverage-v8-4.1.7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github May 25, 2026

Copy link
Copy Markdown
Contributor

Bumps @vitest/coverage-v8 from 3.2.4 to 4.1.7.

Release notes

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

v4.1.7

   🐞 Bug Fixes

    View changes on GitHub

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub

v4.1.5

   🚀 Experimental Features

   🐞 Bug Fixes

    View changes on GitHub

v4.1.4

   🚀 Experimental Features

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​vitest/coverage-v8 since your current version.


Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@coderabbitai

coderabbitai Bot commented May 25, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Summary by CodeRabbit

  • Chores
    • Updated test coverage tool dependency to the latest version.

Walkthrough

This PR updates the @vitest/coverage-v8 development dependency in package.json from version ^3.2.4 to ^4.1.7. This is a minor version bump that brings in a newer version of the Vitest code coverage tool for v8, allowing the project to access recent improvements and bug fixes in the coverage instrumentation tooling.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description lacks the required template sections. Missing are the 'Changes' section describing what was changed and the 'Checklist' with release label selection and verification items. Add the required 'Changes' and 'Checklist' sections from the template. Select an appropriate release label (major, minor, patch, or skip-release) and confirm documentation and test updates.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the main change: bumping @vitest/coverage-v8 from version 3.2.4 to 4.1.7, which is the primary objective of the PR.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dependabot/npm_and_yarn/vitest/coverage-v8-4.1.7

Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

📥 Commits

Reviewing files that changed from the base of the PR and between b6fa312 and 8fa1abb.

📒 Files selected for processing (1)
  • package.json

Comment thread package.json
"@types/node": "^25.0.2",
"@types/tmp": "^0.2.6",
"@vitest/coverage-v8": "^3.2.4",
"@vitest/coverage-v8": "^4.1.7",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 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 --json

Repository: 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.

@dependabot @github

dependabot Bot commented on behalf of github Jun 2, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #291.

@dependabot dependabot Bot closed this Jun 2, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/vitest/coverage-v8-4.1.7 branch June 2, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants