[release/6.0] SDL: Resolve component governance warnings. #8359
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 characters
* Update the version of Microsoft.Data.OData * Fix the syntax * Update Microsoft.Data.Services.Client as well
riarenas
requested review from
Chrisboh,
garath,
michellemcdaniel and
mmitche
michellemcdaniel
approved these changes
Jan 19, 2022
mmitche
approved these changes
Jan 19, 2022
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.
https://github.com/dotnet/core-eng/issues/15376
Description
This ports two commits to update package versions and resolve component governance warnings:
I validated this change in this official build: https://dnceng.visualstudio.com/internal/_build/results?buildId=1560913&view=results, and the CG alerts for this branch no longer include any high severity alerts: https://dnceng.visualstudio.com/internal/_componentGovernance/dotnet-arcade?_a=alerts&typeId=10387791&alerts-view-option=active
Customer Impact
Once CG is turned on for 6.0 branches repos with an out of date arcade will most likely get CG alerts related to this.
Regression
No
Risk
Low risk. These changes were already ported to the release/5.0 branch and have been in main for a while.
Workarounds
None.