[release/8.0.1xx] Update AnalyzerReleases file to reflect new analyzers for .NET8 release #6944
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.
Backport of #6940 to release/8.0.1xx
Customer Impact
Shipped releases in AnalyzerReleases.Shipped.md is used to drive the auto-generation of editorconfig files that ship with the analyzer NuGet package and the .NET SDK and are passed down to the compiler based on the
AnalysisLevel
MSBuild property. This PR is needed to ensure that settingAnalysisLevel = 8
includes the new analyzers added with this release.Testing
I have verified that locally built Microsoft.CodeAnalysis.NetAnalyzers NuGet package includes these new analyzers added in .NET8 timeframe in the editorconfig files generated for AnalysisLevel 8.
Risk
This should be a pretty low risk fix, something we do at the time of branching every new release branch on this repo for a new .NET release. For example, see #6246 that was checked in for .NET 7 release