Update dependency Microsoft.CodeAnalysis.CSharp to v5

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.CodeAnalysis.CSharp	4.14.0 → 5.3.0

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[github-actions]

Test Results

0 tests  ±0   0 ✅ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit b1fddb6. ± Comparison against base commit 2429901.

♻️ This comment has been updated with latest results.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

AI Reviewer: first review requested successfully. AI can make mistakes. Always validate suggestions.

_{TIP This summary will be updated as you push new changes.}

[codacy-production]

Pull Request Overview

While the dependency update itself follows standard practices, it creates a direct conflict with the project's naming convention and apparent version-specific architecture. The project file Indago.Analyzers.roslyn4.8.csproj is explicitly named to reflect Roslyn 4.8 support, but the dependency is being moved to 5.3.0.

This misalignment should be resolved before merging. You must either rename the project and update its references to reflect version 5.x or revert the update if this project is strictly intended for 4.8 compatibility. Despite the Codacy analysis being 'up to standards', this naming contradiction represents a maintenance risk.

About this PR

• There is a systemic naming inconsistency: the project is named 'roslyn4.8', but it is now being configured to use Roslyn 5.3.0. This suggests the project structure may need a broader update to support multiple Roslyn versions or a full migration to the newer version including file renaming.

Test suggestions

• Verify project builds successfully with the updated Roslyn 5.3.0 dependency

Prompt proposal for missing tests

Consider implementing these tests if applicable:
1. Verify project builds successfully with the updated Roslyn 5.3.0 dependency

_{TIP Improve review quality by adding custom instructions
TIP How was this review? Give us feedback}

[codacy-production]

_{🟡 MEDIUM RISK}

The package version (5.3.0) contradicts the project's filename 'Indago.Analyzers.roslyn4.8.csproj'. If this project is specifically intended to support Roslyn 4.8, this update should not be applied. However, if the project is migrating to version 5, the file should be renamed to reflect the new target version and all related solution and project references must be updated. Suggested action: Rename the project file to 'Indago.Analyzers.roslyn5.csproj' or similar and verify all dependent references.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.