Conversation
vitest@5.0.0's published engines.node is "^22.12.0 || ^24.0.0 || >=26.0.0" (checked via npm view) — it won't run below Node 22.12. 26 is the next even-major LTS-track ceiling.
vitest and @vitest/coverage-v8 peer each other exactly, so opening separate PRs for each breaks npm ci with an ERESOLVE the moment one bumps without the other. Group them so future bumps land together in one PR.
@eslint/js peers eslint with a major-locked range ("^10.0.0"), and
@cldmv/prettier-plugin-jsonv peers prettier the same way ("^3.0.0")
-- both verified via npm view, not memory. Neither is broken today,
but a future major bump would hit the same npm ci ERESOLVE class the
vitest + @vitest/coverage-v8 split just did. Group them proactively.
cldmv-bot
Bot
added
! release → master
Contributor
Author
🔒 Dependency Review
|
cldmv-bot
Bot
added
type: ci
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 4.1.11 to 5.0.0. - [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/v5.0.0/packages/vitest) --- updated-dependencies: - dependency-name: vitest dependency-version: 5.0.0 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
@vitest/coverage-v8 peers vitest with a major-locked range, so Dependabot's separate vitest-only bump (this branch) broke npm ci with an ERESOLVE until coverage-v8 moved too. `@dependabot recreate` does not re-group an already-opened single-package PR against a newly added dependabot.yml group -- it just refreshes that PR's own single-package update, so this had to be applied by hand.
Shinrai
approved these changes
Sep 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🚀 What's Changed
💥 Breaking Changes
No breaking changes
✨ Features
No new features
🐛 Bug Fixes
No bug fixes
📦 Dependencies
🔧 Other Changes
👥 Contributors
Avg: 100.0% ·
1b3bfa5· Node lts/*