Skip to content

Conversation

@dsplaisted
Copy link
Member

This broke with #27199

…013.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22513.4
…014.3

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22514.3
…031.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22531.4
…107.1

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22557.1
…108.4

Microsoft.DotNet.Arcade.Sdk , Microsoft.DotNet.Helix.Sdk , Microsoft.DotNet.SignTool , Microsoft.DotNet.XUnitExtensions
 From Version 7.0.0-beta.22511.2 -> To Version 7.0.0-beta.22558.4
@ghost
Copy link

ghost commented Nov 10, 2022

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@dsplaisted dsplaisted force-pushed the fix-normalize-windows-platform-version branch 2 times, most recently from 7e7930d to b0d6e99 Compare November 11, 2022 20:04
@dsplaisted
Copy link
Member Author

FYI @j0shuams

@dsplaisted dsplaisted changed the base branch from release/7.0.1xx to release/7.0.2xx November 14, 2022 16:58
@dsplaisted dsplaisted requested a review from a team as a code owner November 14, 2022 16:58
This broke with changes related to dotnet#27199.
It's now possible to have multiple supported platform version items for the
same version.
Depending on whether we're using preview versions, some of the packages
may be downloaded by NuGet and have lowercased names, while at other
times they may be shipped in the packs folder and have mixed case.
@dsplaisted dsplaisted force-pushed the fix-normalize-windows-platform-version branch from b0d6e99 to 91b88f3 Compare November 14, 2022 17:05
@dsplaisted
Copy link
Member Author

This was rejected for servicing as the customer impact is low to nonexistent, so I've re-targeted it to 7.0.2xx.

@dsplaisted
Copy link
Member Author

@nagilson Care to review this so we can merge it now?

Copy link
Member

@nagilson nagilson left a comment

Choose a reason for hiding this comment

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

@dsplaisted I looked at the code and it seemed good, but I didn't see any test that tested this specific regression:
A TargetPlatformVersion property for Windows without a trailing “.0” won’t be normalized to 4 version sections anymore (for example from 10.0.18362 to 10.0.18362.0). Am I wrong that this is related to that?

The test changes I saw were just handling case-sensitivity, was a regression test added to check for the .0 behavior? I know some other tests (might) fail if it's wrong already.

@dsplaisted
Copy link
Member Author

@nagilson The test is It_succeeds_if_windows_target_platform_version_does_not_have_trailing_zeros. There's no update to it in this PR, because this PR fixes the regression that caused the test to fail. You can see it is one of the tests disabled in the 7.0.1xx PR: #28591

@dsplaisted dsplaisted merged commit 22c1f98 into dotnet:release/7.0.2xx Nov 15, 2022
@nagilson
Copy link
Member

Gotcha, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants