[release/2.1] Bump package version for S.S.C.Pkcs and add it to packages.builds#32111
[release/2.1] Bump package version for S.S.C.Pkcs and add it to packages.builds#32111bartonjs wants to merge 2 commits intodotnet:release/2.1from
Conversation
DescriptionPackage authoring was missing from System.Security.Cryptography.Pkcs for previous release/2.1 changes, resulting in those changes not shipping. Customer ImpactCustomers are still affected by bugs that we fixed. Regression?Some of the bugs were regressions from .NET Framework, but this particular change is not a regression. RiskLow. The changes have been tested with unit tests for a while, we just didn't actually release them. |
|
It would be good to do a "allconfigurations" build locally to verify the package is built with the expected versions. |
Need to update the package index as well. |
|
@weshaggard UpdatePackageIndex made some unrelated changes. I left them in, rather than fight with the tool; but can certainly edit them back out. |
They are just normalization so it is fine to leave them in. |
|
@dotnet-bot Test OSX x64 Debug Build please (timeout in System.Net.Security.Tests.ServerAsyncAuthenticateTest.ServerAsyncAuthenticate_EachSupportedProtocol_Success(protocol: Tls11)) |
|
Obsoleted by #32203 |
This package authoring was missing from the changes for 2.1.3 servicing, resulting in those fixes not making it to customers.
Fixes #32092.