chore(deps)!: migrate vitest ^4.1.10 → ^5.0.0 - #184
Merged
Merged
Conversation
|
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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.
Migration:
vitest^4.1.10→^5.0.0This breaks the existing constraint, so it is not a routine bump — the package is signalling a breaking change. Generator code or templates may need to change alongside it.
CI will tell you: if test-flows passes as-is, this is just a version bump after all. If it fails, that failure is the work.
This branch is yours now — the bot will not touch it again. Leaving this PR open tells the bot you have this in hand, and keeps
vitestout of the Rollup.🤖 dep-checker