Repository navigation
Fix remaining tooling security advisories and validate packaging - #84
Merged
Merged
Conversation
Merged
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.
The dependency audit still flagged MSAL Node, qs, minimatch, and Mocha's nested glob after the latest upgrades. This clears those advisories while preserving a working build and packaging toolchain.
Validation: clean npm ci; npm audit reports zero vulnerabilities; npm ls confirms the patched versions without invalid dependencies; compile and lint pass; all three integration tests pass on VS Code 1.144.0; VSIX packaging succeeds with the expected nine files. Cross-platform CI uses Node 22.
The minimatch and Mocha glob overrides cross major-version ranges and should be removed when their upstream consumers adopt patched versions. Extension runtime code is unchanged.