This repository was archived by the owner on Jan 5, 2026. It is now read-only.
fix: node-fetch Component Governance vulnerability#4079
Merged
BruceHaley merged 9 commits intomainfrom Feb 11, 2022
Merged
Conversation
Pull Request Test Coverage Report for Build 1826987990
💛 - Coveralls |
BruceHaley
added
the
Area: Engineering
added 4 commits
January 31, 2022 16:42
mrivera-ms
approved these changes
Feb 2, 2022
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes #minor
Description
Fixes the high severity node-fetch vulnerability listed in this CG alert:
https://fuselabs.visualstudio.com/SDK_v4/_componentGovernance/112352/alert/6435491?typeId=10220548
Vulnerability: Upgrade node-fetch from 2.6.1 to 2.6.7 to fix the vulnerability.
Force node-fetch to v 2.6.7
Specific Changes
Add a resolutions section to the root package.json.