From 86900937ba371204e55494bbb76fa3544d69a28c Mon Sep 17 00:00:00 2001
From: Paul Medynski <31868385+paulmedynski@users.noreply.github.com>
Date: Mon, 15 Jun 2026 21:05:40 -0300
Subject: [PATCH] Switch SDK rollForward from disable to patch for automatic
 servicing updates (#4364)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

* Switch SDK rollForward from disable to patch

Allow automatic roll-forward within the 10.0.3xx feature band so that
servicing patches (e.g. security fixes like 10.0.301) are picked up by
CI agents and developers without requiring a dedicated PR for each bump.

The base version remains 10.0.300 — this is the minimum required SDK.
Any installed 10.0.3xx patch will be used automatically.

Updated both global.json files:
- /global.json (repo root)
- /tools/PackageCompatibility/global.json

* Re-worded SDK comment.
---
 global.json | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/global.json b/global.json
index 48cbbf1a80..bf6c9e3e32 100644
--- a/global.json
+++ b/global.json
@@ -4,13 +4,14 @@
     // We currently require the .NET 10 SDK to build and test the project.
     //
     // GOTCHA: Our CI infrastructure for Windows uses VS 2022 which comes with MSBuild 17.x.  The
-    // .NET 10 SDK versions in the 10.0.2xx series require MSBuild 18.x, so we specify the most
-    // recent 10.0.1xx series release which is compatible with MSBuild 17.x.
+    // .NET 10 SDK versions in the 10.0.2xx series require MSBuild 18.x, so we stick with the
+    // 10.0.1xx feature band which is compatible with MSBuild 17.x.
     //
-    "version": "10.0.107",
+    "version": "10.0.100",
 
-    // We cannot allow any roll forward due to the above MSBuild compatibility issues.
-    "rollForward": "disable",
+    // Allow roll-forward within the 10.0.1xx feature band so servicing patches
+    // are picked up automatically without requiring a PR for each bump.
+    "rollForward": "patch",
 
     // Do not allow pre-release versions.
     //