Bump @vitest/coverage-v8 from 3.2.4 to 4.0.18#358
Bump @vitest/coverage-v8 from 3.2.4 to 4.0.18#358dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
dependabot
bot
requested review from
CarlosGamero and
kibertoad
as code owners
|
Note
|
| Cohort / File(s) | Summary |
|---|---|
Dependency Version Update package.json |
Bumped devDependency @vitest/coverage-v8 from ^3.2.4 to ^4.0.18. |
Estimated code review effort
🎯 1 (Trivial) | ⏱️ ~2 minutes
🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
| Check name | Status | Explanation | Resolution |
|---|---|---|---|
| Description check | The description is incomplete according to the required template. While it contains detailed release notes and change information, it is missing the required 'Changes' section describing the changes and does not include the required 'Checklist' with labels (major/minor/patch/skip-release), documentation updates, and test updates. | Add a 'Changes' section describing the update, and include the checklist with appropriate label selection, documentation/test update confirmations as specified in the template. |
✅ Passed checks (2 passed)
| Check name | Status | Explanation |
|---|---|---|
| Title check | ✅ Passed | The title clearly and specifically describes the main change: bumping the @vitest/coverage-v8 dependency from version 3.2.4 to 4.0.18, which matches the changeset exactly. |
| 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.
✨ Finishing touches
🧪 Generate unit tests (beta)
- Create PR with unit tests
- Post copyable unit tests in a comment
- Commit unit tests in branch
dependabot/npm_and_yarn/vitest/coverage-v8-4.0.18
No actionable comments were generated in the recent review. 🎉
Comment @coderabbitai help to get the list of available commands and usage tips.
![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
🤖 Fix all issues with AI agents
In `@package.json`:
- Line 73: The dependency mismatch: update the vitest dependency to match
`@vitest/coverage-v8` by changing the "vitest" entry to "^4.0.18" so it aligns
with "@vitest/coverage-v8": "^4.0.18", ensuring the peer requirement is
satisfied; locate the "vitest" key in package.json and bump its version string
to "^4.0.18".
| "@types/newrelic": "^9.14.8", | ||
| "@types/node": "^24.7.0", | ||
| "@vitest/coverage-v8": "^3.2.4", | ||
| "@vitest/coverage-v8": "^4.0.18", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
@vitest/coverage-v8 4.0.18 peer dependencies vitest
💡 Result:
For @vitest/coverage-v8@4.0.18, the vitest peer dependency is an exact match:
peerDependencies.vitest:"4.0.18"(required)peerDependencies.@vitest/browser:"4.0.18"(optional; only needed for browser mode)
This follows Vitest’s pattern of pinning peer deps to the same exact version (e.g., 4.0.2 and 4.0.13 both pin vitest to the identical version). [1], [2]
Sources: [1] [2]
Version mismatch: @vitest/coverage-v8@4.0.18 requires vitest@4.0.18 (exact match).
The @vitest/coverage-v8 package is being bumped to 4.0.18, which requires vitest@4.0.18 exactly. However, vitest on line 84 remains at ^3.2.4, making them incompatible. Vitest packages pin peer dependencies to exact versions, not just matching major versions.
Update vitest to ^4.0.18 to match @vitest/coverage-v8.
🤖 Prompt for AI Agents
In `@package.json` at line 73, The dependency mismatch: update the vitest
dependency to match `@vitest/coverage-v8` by changing the "vitest" entry to
"^4.0.18" so it aligns with "@vitest/coverage-v8": "^4.0.18", ensuring the peer
requirement is satisfied; locate the "vitest" key in package.json and bump its
version string to "^4.0.18".
bb4f606 to
8cb3326
Compare
Bumps [@vitest/coverage-v8](https://github.com/vitest-dev/vitest/tree/HEAD/packages/coverage-v8) from 3.2.4 to 4.0.18. - [Release notes](https://github.com/vitest-dev/vitest/releases) - [Commits](https://github.com/vitest-dev/vitest/commits/v4.0.18/packages/coverage-v8) --- updated-dependencies: - dependency-name: "@vitest/coverage-v8" dependency-version: 4.0.18 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/vitest/coverage-v8-4.0.18
branch
from
8cb3326 to
11c2bfe
Compare
|
Superseded by #376. |
dependabot
bot
deleted the
dependabot/npm_and_yarn/vitest/coverage-v8-4.0.18
branch
Bumps @vitest/coverage-v8 from 3.2.4 to 4.0.18.
Release notes
Sourced from
@vitest/coverage-v8's releases.... (truncated)
Commits
4d3e3c6chore: release v4.0.18dd54e94chore: 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.12Maintainer 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