From 57604fc279fe63eb5885325ee5c15c8bac0dbf96 Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 7 Sep 2026 06:23:55 +0000
Subject: [PATCH 1/2] Bump the dotnet group with 2 updates

Bumps TUnit from 1.19.16 to 1.66.16
Bumps Verify.TUnit from 31.13.2 to 32.0.0

---
updated-dependencies:
- dependency-name: TUnit
  dependency-version: 1.66.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Verify.TUnit
  dependency-version: 32.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: dotnet
...

Signed-off-by: dependabot[bot] <support@github.com>
---
 MarkupString.Tests/MarkupString.Tests.csproj | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/MarkupString.Tests/MarkupString.Tests.csproj b/MarkupString.Tests/MarkupString.Tests.csproj
index be18727..140f8f1 100644
--- a/MarkupString.Tests/MarkupString.Tests.csproj
+++ b/MarkupString.Tests/MarkupString.Tests.csproj
@@ -9,12 +9,12 @@
   </PropertyGroup>
   <ItemGroup>
     <PackageReference Include="CsCheck" Version="4.8.0" />
-    <PackageReference Include="TUnit" Version="1.19.16" />
+    <PackageReference Include="TUnit" Version="1.66.16" />
     <!-- Pinned to the newest Verify.TUnit whose TUnit.Core floor (1.16.4) stays under this
          repo's TUnit 1.19.16. Verify.TUnit 31.13.3+ floors TUnit.Core at 1.19.57, which NuGet
          lifts above TUnit.Engine 1.19.16 and the split versions fault at startup with
          MissingFieldException: TUnit.Core.Sources.BeforeEveryTestHooks. -->
-    <PackageReference Include="Verify.TUnit" Version="31.13.2" />
+    <PackageReference Include="Verify.TUnit" Version="32.0.0" />
   </ItemGroup>
   <ItemGroup>
     <ProjectReference Include="..\MarkupString\MarkupString.csproj" />

From 2c9cbf9f2bf71473cf28d20d4d583ca560082b7d Mon Sep 17 00:00:00 2001
From: Harry Cordewener <admin@twilightdays.org>
Date: Mon, 7 Sep 2026 01:37:55 -0500
Subject: [PATCH 2/2] Say what the Verify.TUnit/TUnit constraint actually is

The comment beside the reference described a pin that this bump removes, naming
versions that are no longer in the file. What survives the bump is the reason
the two have to move together, so state that and nothing else.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 MarkupString.Tests/MarkupString.Tests.csproj | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/MarkupString.Tests/MarkupString.Tests.csproj b/MarkupString.Tests/MarkupString.Tests.csproj
index 140f8f1..273b214 100644
--- a/MarkupString.Tests/MarkupString.Tests.csproj
+++ b/MarkupString.Tests/MarkupString.Tests.csproj
@@ -10,10 +10,9 @@
   <ItemGroup>
     <PackageReference Include="CsCheck" Version="4.8.0" />
     <PackageReference Include="TUnit" Version="1.66.16" />
-    <!-- Pinned to the newest Verify.TUnit whose TUnit.Core floor (1.16.4) stays under this
-         repo's TUnit 1.19.16. Verify.TUnit 31.13.3+ floors TUnit.Core at 1.19.57, which NuGet
-         lifts above TUnit.Engine 1.19.16 and the split versions fault at startup with
-         MissingFieldException: TUnit.Core.Sources.BeforeEveryTestHooks. -->
+    <!-- Verify.TUnit carries a floor on TUnit.Core. Bump the two together: if NuGet lifts
+         TUnit.Core past the TUnit.Engine this project asks for, the split versions fault at
+         startup with MissingFieldException rather than failing to restore. -->
     <PackageReference Include="Verify.TUnit" Version="32.0.0" />
   </ItemGroup>
   <ItemGroup>