Repository navigation
build(deps): resolve vite 7.3.7 for vitest - #54
Merged
Merged
Conversation
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.
Adds
vite ^7.3.7as a dev dependency so vitest resolves the patched vite. That closes the one open Dependabot alert, GHSA-698v-4r3x-3vcv (vite 7.0.0 to 7.3.6).vitest 5 takes vite as an auto-installed peer, so the lock only moves once vite is a direct dev dependency; guard-core-ts got the same fix in #171. Only vite moves in
pnpm-lock.yaml: 7.3.6 to 7.3.7 plus the vitest and@vitest/mockerentries that reference it. The published package does not change, since vite is dev only.Checked locally, the way
ci.ymlruns it:pnpm install --frozen-lockfile,pnpm lintandpnpm build: exit 0pnpm test:coverage: 22 files, 300 tests passed, coverage 100/100/100/100pnpm audit --audit-level=low: no known vulnerabilities