chore: Fix Component Governance alert for nconf #4213
Merged
Conversation
This file contains 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
BruceHaley
added
the
Automation: No parity
BruceHaley
changed the title
Pull Request Test Coverage Report for Build 2242940179
💛 - Coveralls |
tracyboehrer
approved these changes
Apr 29, 2022
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.
Fixes #4188
Description
Branch main has 2 code governance alerts with high severity or above:
This fixes nconf. minimist requires a new release of orchestrator-core. (That release is ready to go.)
Specific Changes
Bump nconf to 0.11.4.
Update dependency @microsoft/orchestrator-core to latest: 4.14.3.
Update yarn.lock to match changes.
Cleanup and infrastructure tweak:
Drop an irrelevant package-lock.json file.
Add Component Detection to streaming E2E tests pipeline.