Fixes Microsoft.NETCore.App.Runtime Component Governance issues #8880
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
jaredpar
approved these changes
Jun 28, 2023
phil-allen-msft
approved these changes
Jun 28, 2023
jjonescz
approved these changes
Jun 28, 2023
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.
Summary of the changes
When building a .NET core app we implicitly pull down references for the runtime. e.g.
Microsoft.NetCore.App.Runtime.linux-armwhen building for Linux. At the moment our builds are pulling down 7.0.5 but CG is asking to be 7.0.7.So this PR updates MicrosoftAspNetCoreAppVersion to 7.0.7.
Here is a recent Component Governance - Compliance (visualstudio.com) report: Pipelines - Run 20230624.1 (visualstudio.com) taken from merged PR #8863.
The report shows the
Microsoft.NETCore.App.Runtime.win-arm64items are still showing up after the arcade update already merged in PR #8762)).