Repository navigation
chore: Remediate 2 Dependabot security alerts (lockfile only) - #95
Merged
Merged
Conversation
Update vitest and @vitest/* from 4.1.11 to 4.1.12 to resolve GHSA-qxg6-89mg-rqv8 and GHSA-xp26-3454-mjgp in @vitest/mocker.
gethinwebster
approved these changes
Nov 2, 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.
Updates
vitestand the@vitest/*packages from 4.1.11 to 4.1.12 (lockfile only) to resolve 2 of the 3 open security alerts in this repository.Merging this PR resolves the 2 alerts listed below. It leaves 1 alert open (see "Not resolved"). There are no other open Dependabot PRs in this repository.
Alerts addressed
@vitest/mocker, medium, 4.1.11 -> 4.1.12@vitest/mocker, medium, 4.1.11 -> 4.1.12How it was fixed
@vitest/mockeris a transitive dependency ofvitest, which is already a direct dev dependency, so the patched release is reached by updatingvitestand the packages released with it.package.jsonis unchanged because the existing range (^4.1.11) already allows 4.1.12.The diff is limited to the 9
vitestfamily entries inpackage-lock.json(vitest,@vitest/coverage-v8,expect,mocker,pretty-format,runner,snapshot,spy,utils). All are dev dependencies.Not resolved
minimatch, medium,< 11.0.1. The only patched release is 11.0.1, a new major version. The vulnerable copy (10.2.6) comes from@typescript-eslint/typescript-estree, whose latest release (8.72.1) still requiresminimatch ^10.2.2, so no parent update reaches the fix. Resolving it would take apackage.jsonoverridesentry forcing a major version past what the parent declares, which needs a maintainer decision.Verification
Run locally on this commit:
npm run buildandnpm testboth pass (13 test files, 145 tests).