ci: upgrade to vitest 5 - #127
Merged
Merged
Conversation
Both were provided transitively by vitest's vite: vite@8 pulled rolldown to the top level, satisfying tsdown's rolldown-plugin-dts peer import, and vitest depended on vite directly. legacy-peer-deps hides these, so the upcoming vitest 5 bump (vite becomes a peer, rolldown is no longer hoisted) would break the build and test runner. Declare both directly to decouple the build from vitest's dependency tree. Assisted-by: Claude:claude-opus-4-8
Combines dependabot #126 and #125, which must move in lockstep. vite and rolldown are already declared directly (previous commit), so the v5 tree resolves cleanly under legacy-peer-deps. Also drops the @vitest/mocker path traversal advisory (GHSA-82fw-gwwq-j7x9) that shipped with vitest 4. Assisted-by: Claude:claude-opus-4-8
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 kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Upgrade vitest to v5.
Does this PR introduce a breaking change?
No.
Other information