Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix CG issue for Microsoft.IO.Redist #74653

Merged
merged 2 commits into from
Aug 8, 2024
Merged

Fix CG issue for Microsoft.IO.Redist #74653

merged 2 commits into from
Aug 8, 2024

Conversation

jaredpar
Copy link
Member

@jaredpar jaredpar commented Aug 5, 2024

Move to a version with the appropriate fix

The explicit ref of Microsoft.IO.Redist is required because of dotnet/sdk#42608

@jaredpar jaredpar requested a review from a team as a code owner August 5, 2024 22:16
@dotnet-issue-labeler dotnet-issue-labeler bot added Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead labels Aug 5, 2024
@jaredpar jaredpar enabled auto-merge (squash) August 5, 2024 22:19
jaredpar added a commit to dotnet/razor that referenced this pull request Aug 7, 2024
This should make it much easier for us to respond to CG alerts in the
future. All that will need to be done is add an entry in
Directory.Packages.props and it will automatically impact all consumers
of it.

Consider this example in Roslyn for how to respond to a CG issue

dotnet/roslyn#74653
Move to a version with the appropriate fix
@jaredpar jaredpar requested a review from a team as a code owner August 7, 2024 23:32
@@ -34,6 +34,7 @@
<PackageReference Include="System.CommandLine" />
<PackageReference Include="System.Collections.Immutable" />
<PackageReference Include="Newtonsoft.Json" />
<PackageReference Include="Microsoft.IO.Redist" Condition="'$(TargetFrameworkIdentifier)' != '.NETCoreApp'" />
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Womp

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's busted you have to do this, you want all of MSBuild to be Exclude="Runtime"

I wonder if instead of referencing the packages for MSBuild which bring in it's entire NuGet graph, you could just reference the API it exposes. As reference assemblies. cc @baronfel

@jaredpar jaredpar merged commit d1fe9e9 into dotnet:main Aug 8, 2024
28 checks passed
@dotnet-policy-service dotnet-policy-service bot added this to the Next milestone Aug 8, 2024
@jaredpar jaredpar deleted the cg branch August 8, 2024 02:46
jaredpar added a commit to dotnet/razor that referenced this pull request Aug 9, 2024
* Move to central package pinning

This should make it much easier for us to respond to CG alerts in the
future. All that will need to be done is add an entry in
Directory.Packages.props and it will automatically impact all consumers
of it.

Consider this example in Roslyn for how to respond to a CG issue

dotnet/roslyn#74653
@dibarbet dibarbet modified the milestones: Next, 17.12 P2 Aug 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants