fix(state): bump vitest to ^4.1.0 in module-state, resolving Dependabot alerts #382/#377 - #5217
Merged
Merged
Conversation
🦋 Changeset detectedLatest commit: 04b6f72 The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Contributor
Coverage Report
File CoverageNo changed files found. |
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
Bumps
vitestinpackages/modules/statefrom^2.0.5to^4.1.0(dev dependency, test runner only), matching the version already used across the rest of the monorepo.Why
Resolves Dependabot security alerts #382/#377 (Vitest UI server arbitrary file read/execute vulnerability, affects
< 3.2.6).packages/modules/statewas the one package still resolving to the vulnerablevitest@2.1.9.Supersedes #5212
Dependabot's own PR (#5212, closed) targeted the same alert but was based on a stale
mainsnapshot — merging it as-is would have regressed 25 other packages from^4.1.0back down to^3.2.6. This PR is a narrower, non-regressive fix scoped to just the one package that actually needed it.Validation
tsc -bcleanpnpm install --frozen-lockfileconfirms lockfile consistencypnpm why vitestconfirms resolution tovitest@4.1.10, clear of the vulnerable rangeleveldownnative-binding issue (reproduces onmaintoo, environment-only, not a regression from this change)Changeset included (patch bump).