build: upgrade Roslynator.Refactorings from 4.16.1 to 5.0.0

[dependabot]

Updated Roslynator.Refactorings from 4.16.1 to 5.0.0.

Release notes

Sourced from Roslynator.Refactorings'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)

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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)