From c7f1bd14178dea3ce809cfb0fbe2db4d7dedda52 Mon Sep 17 00:00:00 2001
From: Glenn Watson <5834289+glennawatson@users.noreply.github.com>
Date: Sun, 2 Aug 2026 14:18:44 +1000
Subject: [PATCH] chore(renovate): hold the generator and analyzer at the
 Roslyn baseline

- Microsoft.CodeAnalysis.CSharp and .CSharp.Workspaces no longer receive update
  PRs. Both ship in the version-less analyzers/dotnet/cs folder, and a compiler
  refuses to load a generator built against a newer Roslyn than itself, so
  raising the 4.8.0 floor drops every consumer on an older SDK.
- Microsoft.CodeAnalysis.Analyzers keeps moving; it supplies analyzer-authoring
  rules and has no bearing on the load floor.
---
 .github/renovate.json | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/.github/renovate.json b/.github/renovate.json
index 7d858dd..9434a6e 100644
--- a/.github/renovate.json
+++ b/.github/renovate.json
@@ -4,6 +4,17 @@
         "local>reactiveui/.github:renovate"
     ],
     "packageRules": [
+        {
+            "description": "The generator and analyzer are held at the Roslyn 4.8.0 baseline (VS 2022 17.8, .NET 8.0.1xx SDK) and must not move with the toolchain. Both ship in the version-less analyzers/dotnet/cs folder, and a compiler refuses to load a generator or analyzer built against a newer Roslyn than itself, so raising this floor silently drops every consumer on an older SDK. It is a compatibility decision, not a maintenance lag, and the only reason to change it is to raise the minimum supported SDK on purpose. Microsoft.CodeAnalysis.Analyzers is deliberately absent: it supplies analyzer-authoring rules and has no bearing on the load floor.",
+            "matchManagers": [
+                "nuget"
+            ],
+            "enabled": false,
+            "matchPackageNames": [
+                "/^Microsoft\\.CodeAnalysis\\.CSharp$/",
+                "/^Microsoft\\.CodeAnalysis\\.CSharp\\.Workspaces$/"
+            ]
+        },
         {
             "description": "Analyzer packages all gate the build through the same warnings-as-errors pass, so landing them separately just means several red CI runs in a row. Move them in one PR.",
             "matchManagers": [