Repository navigation
chore: 🔨 Update dependencies - vitest - #605
Merged
Merged
Conversation
c-kruse
approved these changes
Sep 24, 2026
fgiorgetti
approved these changes
Sep 29, 2026
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.
Description
Fixes a critical vulnerability (Dependabot alert #169) by bumping
vitestand@vitest/coverage-v8from^3.1.3to^3.2.7inpackage.json..npmrcand.yarnrcare added to.gitignoreto prevent accidental commits of local registry configuration files.Additional context (optional)
This upgrade addresses a critical security vulnerability reported by Dependabot. Vitest
3.2.xalso includes bug fixes, performance improvements, and new features over3.1.x. Keeping these two packages in sync ensures compatibility between the test runner and the coverage provider.The
.npmrc/.yarnrcexclusions prevent developer-specific registry overrides (e.g. corporate Artifactory proxies) from being accidentally committed to the repository.How to test
yarn test