chore(nuget): Bump the analyzers group with 4 updates

[dependabot]

Updated Microsoft.CodeAnalysis.NetAnalyzers from 10.0.302 to 10.0.400.

Release notes

Sourced from Microsoft.CodeAnalysis.NetAnalyzers's releases.

10.0.400

You can build .NET 10.0 from the repository by cloning the release tag v10.0.400 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.303

You can build .NET 10.0 from the repository by cloning the release tag v10.0.303 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Roslynator.Analyzers from 4.16.0 to 5.0.0.

Release notes

Sourced from Roslynator.Analyzers's releases.

5.0.0

Added

• Add roslyn5.0 NuGet package flavor (analyzers/dotnet/roslyn5.0/cs) (PR)

Breaking

• Enable nullable annotations on Roslynator.Common and Roslynator.Workspaces.Common (#​1817)
  • Source-breaking for projects that compile against this surface with nullable reference types enabled.
• [Testing Framework] Lower Roslyn dependency of testing packages to 3.8.0 so that the Roslyn version is determined by the consumer's own Microsoft.CodeAnalysis.* reference instead of being forced to a fixed version (PR)
  • Roslynator.Testing.Common, Roslynator.Testing.CSharp, Roslynator.Testing.CSharp.Xunit and Roslynator.Testing.CSharp.MSTest now depend on Microsoft.CodeAnalysis.* >= 3.8.0 (previously >= 4.14.0).
  • Roslynator.Testing.Common no longer depends on Roslynator.Core.
  • Action required: a test project that previously relied on the testing framework to pull in Roslyn 4.14.0 should now add its own reference, e.g. <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.14.0" />. The chosen version raises the maximum C# language version the parser can accept; test sources still parse at CSharpParseOptions.Default unless you set parse options / LanguageVersion (for example LanguageVersion.Latest).
  • Action required: a test project that used Roslynator.Core types via the old transitive dependency must now add an explicit Roslynator.Core package reference.

Changed

• Bump Roslyn to 5.0.0 (PR)
  • CLI targets Roslyn 5.0.0
  • Solution build and tests use Roslyn 5.0.0 by default (the testing packages floor at 3.8.0; see Breaking)
• Replace Visual Studio 2022 extension with Roslynator 2026 for Visual Studio 2026 ([18.0,19.0)) (PR)
  • Extension ships refactorings and compiler diagnostic code fixes; analyzers via NuGet
  • Roslynator 2022 remains available as the last 4.x VSIX
• Visual Studio Code extension ships refactorings and compiler diagnostic code fixes only (PR)
  • Analyzers require Roslynator NuGet packages
  • Requires OmniSharp with Roslyn 5.x (C# extension 1.39.15+; set dotnet.server.useOmnisharp to true)

Removed

• Remove leftover implementations of obsolete analyzers (XML descriptors remain). Enable the successor rules instead: RCS0014 → RCS0061, RCS0022 → RCS0021, RCS0038 → RCS0015, RCS0043 → RCS0020, RCS0047 → RCS0053, RCS1008/RCS1009/RCS1010/RCS1012/RCS1176/RCS1177 → RCS1264, RCS1035 → RCS1260, RCS1036 → RCS0063, RCS1038/RCS1040/RCS1041/RCS1066/RCS1072/RCS1091/RCS1106 → RCS1259, RCS1063/RCS1064/RCS1065 → RCS1252, RCS1100/RCS1101 → RCS1253, RCS1237 → RCS1254.
• Remove SyntaxInverter (Roslynator.CSharp.Workspaces). Use SyntaxLogicalInverter.
• Remove unused obsolete DiagnosticCategories constants and make the type internal.
• Remove unused ROS0001/ROS0002 diagnostic IDs.
• Remove obsolete constructors/properties from the testing package (DiagnosticTestData, CompilerDiagnosticFixTestData, RefactoringTestData).
• Remove legacy config keys roslynator.max_line_length, roslynator.prefix_field_identifier_with_underscore, and roslynator_suppress_unity_script_methods. Use roslynator_max_line_length, roslynator_prefix_field_identifier_with_underscore, and roslynator_unity_code_analysis.enabled.
• [CLI] Remove obsolete command generate-doc-root. Use generate-doc --root-file-path instead.
• Remove bundled analyzers from Visual Studio extension (PR)
  • Use Roslynator.Analyzers NuGet package for diagnostics
• Remove bundled analyzers from Visual Studio Code extension (PR)
  • Use Roslynator NuGet packages for diagnostics
• Remove AnalyzersOptionsPage from Visual Studio extension (PR)
• Drop support for Visual Studio 2022 VSIX (PR)
  • Pin last 4.x release (Roslynator 2022) or use NuGet packages on Visual Studio 2022

Fixed

• Fix analyzers RCS1263 and RCS1139 for C# 14 extension block documentation (PR)

4.16.1

Fixed

• Fix analyzer RCS1060 to not report a file that contains only multiple partial declarations of the same type (PR)
• Fix analyzer RCS1231 to not suggest in for ref struct parameters (#​1725) (PR)
• Fix analyzer RCS1260 false positive for omit_when_single_line on multi-line object/collection initializers (#​1439) (PR)
• Fix analyzer RCS0036 to report blank lines between single-line declarations in records (PR)
• Fix analyzer RCS1046 to report async void methods without Async suffix (PR)
• Fix analyzer RCS1265 to not report catch clauses with a when filter (PR)
• Fix analyzer RCS0034 for types with a primary constructor and multiple constraint clauses (PR)
• Fix analyzer RCS1231 to not report CancellationToken in sync methods returning Task (PR)
• [CLI] Fix GitLab output format to use relative paths, forward slashes, and 1-based line numbers (PR)
• [CLI] Fix generate-doc to omit internal interfaces from type declarations and the Implements section (PR)

Commits viewable in compare view.

Updated Roslynator.Formatting.Analyzers from 4.16.0 to 5.0.0.

Release notes

Sourced from Roslynator.Formatting.Analyzers's releases.

5.0.0

Added

• Add roslyn5.0 NuGet package flavor (analyzers/dotnet/roslyn5.0/cs) (PR)

Breaking

• Enable nullable annotations on Roslynator.Common and Roslynator.Workspaces.Common (#​1817)
  • Source-breaking for projects that compile against this surface with nullable reference types enabled.
• [Testing Framework] Lower Roslyn dependency of testing packages to 3.8.0 so that the Roslyn version is determined by the consumer's own Microsoft.CodeAnalysis.* reference instead of being forced to a fixed version (PR)
  • Roslynator.Testing.Common, Roslynator.Testing.CSharp, Roslynator.Testing.CSharp.Xunit and Roslynator.Testing.CSharp.MSTest now depend on Microsoft.CodeAnalysis.* >= 3.8.0 (previously >= 4.14.0).
  • Roslynator.Testing.Common no longer depends on Roslynator.Core.
  • Action required: a test project that previously relied on the testing framework to pull in Roslyn 4.14.0 should now add its own reference, e.g. <PackageReference Include="Microsoft.CodeAnalysis.CSharp.Workspaces" Version="4.14.0" />. The chosen version raises the maximum C# language version the parser can accept; test sources still parse at CSharpParseOptions.Default unless you set parse options / LanguageVersion (for example LanguageVersion.Latest).
  • Action required: a test project that used Roslynator.Core types via the old transitive dependency must now add an explicit Roslynator.Core package reference.

Changed

• Bump Roslyn to 5.0.0 (PR)
  • CLI targets Roslyn 5.0.0
  • Solution build and tests use Roslyn 5.0.0 by default (the testing packages floor at 3.8.0; see Breaking)
• Replace Visual Studio 2022 extension with Roslynator 2026 for Visual Studio 2026 ([18.0,19.0)) (PR)
  • Extension ships refactorings and compiler diagnostic code fixes; analyzers via NuGet
  • Roslynator 2022 remains available as the last 4.x VSIX
• Visual Studio Code extension ships refactorings and compiler diagnostic code fixes only (PR)
  • Analyzers require Roslynator NuGet packages
  • Requires OmniSharp with Roslyn 5.x (C# extension 1.39.15+; set dotnet.server.useOmnisharp to true)

Removed

• Remove leftover implementations of obsolete analyzers (XML descriptors remain). Enable the successor rules instead: RCS0014 → RCS0061, RCS0022 → RCS0021, RCS0038 → RCS0015, RCS0043 → RCS0020, RCS0047 → RCS0053, RCS1008/RCS1009/RCS1010/RCS1012/RCS1176/RCS1177 → RCS1264, RCS1035 → RCS1260, RCS1036 → RCS0063, RCS1038/RCS1040/RCS1041/RCS1066/RCS1072/RCS1091/RCS1106 → RCS1259, RCS1063/RCS1064/RCS1065 → RCS1252, RCS1100/RCS1101 → RCS1253, RCS1237 → RCS1254.
• Remove SyntaxInverter (Roslynator.CSharp.Workspaces). Use SyntaxLogicalInverter.
• Remove unused obsolete DiagnosticCategories constants and make the type internal.
• Remove unused ROS0001/ROS0002 diagnostic IDs.
• Remove obsolete constructors/properties from the testing package (DiagnosticTestData, CompilerDiagnosticFixTestData, RefactoringTestData).
• Remove legacy config keys roslynator.max_line_length, roslynator.prefix_field_identifier_with_underscore, and roslynator_suppress_unity_script_methods. Use roslynator_max_line_length, roslynator_prefix_field_identifier_with_underscore, and roslynator_unity_code_analysis.enabled.
• [CLI] Remove obsolete command generate-doc-root. Use generate-doc --root-file-path instead.
• Remove bundled analyzers from Visual Studio extension (PR)
  • Use Roslynator.Analyzers NuGet package for diagnostics
• Remove bundled analyzers from Visual Studio Code extension (PR)
  • Use Roslynator NuGet packages for diagnostics
• Remove AnalyzersOptionsPage from Visual Studio extension (PR)
• Drop support for Visual Studio 2022 VSIX (PR)
  • Pin last 4.x release (Roslynator 2022) or use NuGet packages on Visual Studio 2022

Fixed

• Fix analyzers RCS1263 and RCS1139 for C# 14 extension block documentation (PR)

4.16.1

Fixed

• Fix analyzer RCS1060 to not report a file that contains only multiple partial declarations of the same type (PR)
• Fix analyzer RCS1231 to not suggest in for ref struct parameters (#​1725) (PR)
• Fix analyzer RCS1260 false positive for omit_when_single_line on multi-line object/collection initializers (#​1439) (PR)
• Fix analyzer RCS0036 to report blank lines between single-line declarations in records (PR)
• Fix analyzer RCS1046 to report async void methods without Async suffix (PR)
• Fix analyzer RCS1265 to not report catch clauses with a when filter (PR)
• Fix analyzer RCS0034 for types with a primary constructor and multiple constraint clauses (PR)
• Fix analyzer RCS1231 to not report CancellationToken in sync methods returning Task (PR)
• [CLI] Fix GitLab output format to use relative paths, forward slashes, and 1-based line numbers (PR)
• [CLI] Fix generate-doc to omit internal interfaces from type declarations and the Implements section (PR)

Commits viewable in compare view.

Updated SonarAnalyzer.CSharp from 10.31.0.145097 to 10.33.0.1635.

Release notes

Sourced from SonarAnalyzer.CSharp's releases.

10.33.0.1635

Release notes - .NET Analyzers - 10.33

Feature

NET-4312 Update RSPEC before 10.33 release
NET-4254 Implement rule S9129: "Include" and "ThenInclude" chains of reference navigations should be merged into a single "Include" call

False Positive

NET-1777 Fix S101 FP: Lower case character after number
NET-4245 Fix S107 FP: should not raise for parameters marked with dependency-injection attributes

Maintenance

NET-4184 Duplicate telemetry key exception when multiple projects report the same non-counter telemetry value

10.32.0.713

Release notes - .NET Analyzers - 10.32

Feature

NET-4132 Implement rule S9022: Redundant "Include" calls should be removed
NET-4215 Implement rule S9118: Default values should be compatible with their entity property type
NET-4240 Update RSPEC before 10.32 release

False Positive

NET-1322 Fix S2857 FP: Do not raise in constant string interpolation when string is in square brackets
NET-1468 Fix S6966 FP: should not raise when inside lock
NET-1598 Fix S1125 FP: dynamic and custom nullable structs with conversion to bool are compliant
NET-4233 Fix S8733 FP: AsSplitQuery/AsSingleQuery set in a different statement than the colliding Includes goes undetected
NET-4297 Fix S8717 FP: EFCore DBFirst Scaffold

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Qodana Community for .NET

Analyzed project: src/

It seems all right 👌

No new problems were found according to the checks applied

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.2.0
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions

[codecov-commenter]

⚠️ Please install the to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.75%. Comparing base (de9855c) to head (14b0455).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #389   +/-   ##
=======================================
  Coverage   99.75%   99.75%           
=======================================
  Files          39       39           
  Lines         408      408           
  Branches       46       46           
=======================================
  Hits          407      407           
  Partials        1        1           

Flag	Coverage Δ
unittests	99.50% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.