Skip to content

ci: bump Node CI matrix for vitest 5 (max→26, min→22.12.0) - #22

Merged
Shinrai merged 3 commits into
nextfrom
ci/bump-node-versions-vitest5
Sep 13, 2026
Merged

Shinrai merged 3 commits into
nextfrom
ci/bump-node-versions-vitest5

Conversation

@cldmv-bot

@cldmv-bot cldmv-bot Bot commented Sep 13, 2026 •

Copy link
Copy Markdown
Contributor

🚀 What's Changed

💥 Breaking Changes

No breaking changes

✨ Features

No new features

🐛 Bug Fixes

No bug fixes

📦 Dependencies

No dependency updates

🔧 Other Changes

👥 Contributors

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.
@cldmv-bot cldmv-bot Bot added ! ci → next v4 flow: ci contributor PR targeting the next integration branch type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files labels Sep 13, 2026
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.
@Shinrai
Shinrai merged commit cad5e6a into next Sep 13, 2026
26 checks passed
@cldmv-bot
cldmv-bot Bot deleted the ci/bump-node-versions-vitest5 branch September 13, 2026 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

! ci → next v4 flow: ci contributor PR targeting the next integration branch type: ci Changes to CI workflows, actions, or build pipelines type: config Changes to repository or project configuration files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant