Repository navigation
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 characte
7696
rs
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.
Security update
Upgrade Vitest from 1.x to 5.0.3 and regenerate the npm lockfile. This resolves the critical Vitest UI advisory GHSA-5xrq-8626-4rwp and brings tinypool beyond GHSA-85c8-ppgw-ccpr. The regenerated tree also updates vulnerable
form-dataandwsdependencies.Vitest 5 requires a constructor-compatible
FileReadertest mock; update that mock without changing production behavior.Validation
npm ci --ignore-scripts --no-fundpassed.npm run buildpassed: 20 test files, 377 tests, and extension package generation.npm audit --package-lock-onlyreports zero vulnerabilities, down from 11 dependency-tree findings (2 critical, 7 high, 2 moderate) in the previous lockfile.6dd842c1d478a4e13765e6dbbb3e8497451ea653.GitHub Dependabot alert state still needs verification; the audit counts above are npm findings, not GitHub alert counts.