build(deps): resolve audit vulnerabilities via overrides - #2472
Merged
Conversation
madhavilosetty-intel
force-pushed
the
fix/audit-vulnerabilities-overrides
branch
from
June 30, 2026 19:05
e7e4fca to
220ad57
Compare
Pin vulnerable transitive build-tool dependencies to patched versions through npm overrides.
madhavilosetty-intel
force-pushed
the
fix/audit-vulnerabilities-overrides
branch
from
June 30, 2026 19:08
220ad57 to
26648c0
Compare
madhavilosetty-intel
changed the title
madhavilosetty-intel
enabled auto-merge (squash)
June 30, 2026 19:09
graikhel-intel
approved these changes
Jun 30, 2026
|
🎉 This PR is included in version 11.1.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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
4 participants
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.
Pin vulnerable transitive build-tool dependencies to patched versions through npm overrides.
PR Checklist
What are you changing?
Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. device-management-toolkit/repo#365 )