Repository navigation
fix(deps): patch vulnerable development dependencies - #47
Merged
Merged
Conversation
Lock Vite 8.1.6, Vitest and its coverage plugin 4.1.12, source-map-js 1.2.2 and fast-copy 4.1.0 to clear the advisories the supply-chain scan reports. Declared ranges and the build graph are unchanged.
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
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.
Summary
@vitest/coverage-v8to 4.1.12, source-map-js to 1.2.2, and fast-copy to 4.1.0 inpnpm-lock.yaml. This clears the ten advisories that fail the supply-chain scan onmain.package.jsonstay as they are. Only development dependencies change, and thetsdownand TypeScript build graph is identical, so the package build is unchanged.@vitest/mocker, fixed in 4.1.12.Test plan
osv-scanneronpnpm-lock.yaml: no issues found.