[release/10.0.2xx] Bump analysislevel constants for .NET 10 release#52487
Merged
baronfel merged 2 commits intodotnet:release/10.0.2xxfrom Jan 20, 2026
Merged
[release/10.0.2xx] Bump analysislevel constants for .NET 10 release#52487baronfel merged 2 commits intodotnet:release/10.0.2xxfrom
baronfel merged 2 commits intodotnet:release/10.0.2xxfrom
Conversation
Moving content from unshipped to shipped causes * a set of files for 10 to get created * a set of files for 11 (the unshipped next version) to get created so our tests can pass
jozkee
reviewed
Jan 15, 2026
Member
Author
|
/backport to release/10.0.1xx |
Contributor
|
Started backporting to |
3 tasks
jozkee
approved these changes
Jan 16, 2026
This was referenced Jan 21, 2026
This was referenced Feb 12, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Fixes #52467 for 10.0.2xx
Customer Issue
Customers attempting to use the "latest" analysislevel in the .NET 10 SDK are getting the 9.0 ruleset instead of the 10.0 ruleset. This leads to expected analysis not happening on their projects. The reason for this behavior is that we did not 'advance' the analysis levels as part of TFM bumping to 10 + preparing for stable releases around RC time.
Customers can workaround this by specifying an AnalysisLevel of
preview.Description
This PR:
10for latest and11for preview - the expected values for the .NET 10 releaselatestanalysislevel start working againWas this a regression?
preview)Testing
Added/re-enabled tests that demonstrate correct use of the 10 analysislevel rulesets for projects that use
latest, and use of the 11 rulsesets for projects that usepreview.Risk
Low - the tests cover this logic quite well, and this procedure is one we've done several times in the past.
We'll want to backport for 1xx as well.