Port System.Security.Cryptography.X509Certificates to release/6.0#9097
Port System.Security.Cryptography.X509Certificates to release/6.0#9097jonfortescue merged 2 commits intodotnet:release/6.0from
Conversation
|
@ulisesh has been looking at this in parallel, you should synch as what's in main may not be sufficient yet. |
|
The changes for System.Security.Cryptography.X509Certificates weren't enough and we shouldn't port them |
src/Microsoft.DotNet.Arcade.Sdk/Microsoft.DotNet.Arcade.Sdk.csproj
Outdated
Show resolved
Hide resolved
* Force import of the "right" version so we always restore the version we ask for. * Need to ignore for .proj since these don't have TFMs/restore correctly.
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
What's next for this PR @jonfortescue? |
|
@ulisesh I think this can be merged as is since I am going off FR and we know it resolves the issue it's supposed to. |
|
@jonfortescue can you please hand it off to someone in the FR rotation? |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@ulisesh is something missing on this pr? or is ready to be approved/merged? |
|
This change should be undone. It's causing issues downstream as it's introducing package dependencies in places where they aren't compatible. The fix for CG flagging this package is to address the reference higher in the stack, and only in the projects that cause the problem. |
I'll get this taken care of today and make sure you're on the PR. |
Port #9064 to release/6.0.
To double check: