From 845cf71977c8b63f4628e989c3c90697d3aef48b Mon Sep 17 00:00:00 2001
From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com>
Date: Mon, 21 Sep 2026 16:57:31 +0000
Subject: [PATCH 1/2] Bump the dotnet group with 3 updates

Bumps CsCheck from 4.8.0 to 4.9.1
Bumps TUnit from 1.66.27 to 1.68.17
Bumps Verify.TUnit from 32.0.0 to 33.1.1

---
updated-dependencies:
- dependency-name: CsCheck
  dependency-version: 4.9.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: TUnit
  dependency-version: 1.68.17
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dotnet
- dependency-name: Verify.TUnit
  dependency-version: 33.1.1
  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 | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/MarkupString.Tests/MarkupString.Tests.csproj b/MarkupString.Tests/MarkupString.Tests.csproj
index 64cb666..593ead1 100644
--- a/MarkupString.Tests/MarkupString.Tests.csproj
+++ b/MarkupString.Tests/MarkupString.Tests.csproj
@@ -8,12 +8,12 @@
     <NoWarn>TUnit0038;TUnitAssertions0002</NoWarn>
   </PropertyGroup>
   <ItemGroup>
-    <PackageReference Include="CsCheck" Version="4.8.0" />
-    <PackageReference Include="TUnit" Version="1.66.27" />
+    <PackageReference Include="CsCheck" Version="4.9.1" />
+    <PackageReference Include="TUnit" Version="1.68.17" />
     <!-- 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" />
+    <PackageReference Include="Verify.TUnit" Version="33.1.1" />
   </ItemGroup>
   <ItemGroup>
     <ProjectReference Include="..\MarkupString\MarkupString.csproj" />

From d8a18d0470e87414b67b9a157df85d63b3f62e0f Mon Sep 17 00:00:00 2001
From: Harry Cordewener <admin@twilightdays.org>
Date: Tue, 22 Sep 2026 12:59:41 -0500
Subject: [PATCH 2/2] Answer Verify 33's maintenance-fee check with its
 OpenSource exemption

Verify 33 fails the build without one. MarkupString is open source and earns
nothing, which is the exemption Verify publishes for exactly that. It is
time-bounded to twelve months, so the date has to be renewed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---
 Directory.Build.props | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Directory.Build.props b/Directory.Build.props
index 365a297..8ca024d 100644
--- a/Directory.Build.props
+++ b/Directory.Build.props
@@ -10,6 +10,18 @@
     <AllowUnsafeBlocks>false</AllowUnsafeBlocks>
   </PropertyGroup>
 
+  <!--
+    Verify 33 fails the build unless the consumer answers its maintenance-fee check. MarkupString is
+    open source and earns nothing, which is Verify's own OpenSource exemption. The exemption is
+    time-bounded, at most twelve months out, so this date has to be moved forward (or the answer
+    changed) before it passes — the build says so when it lapses. Verify's terms:
+    https://github.com/VerifyTests/Verify/blob/main/docs/maintenance-fee.md
+  -->
+  <PropertyGroup>
+    <Verify_SponsorshipExemption>OpenSource</Verify_SponsorshipExemption>
+    <Verify_SponsorshipExemptionUntil>2027-09</Verify_SponsorshipExemptionUntil>
+  </PropertyGroup>
+
   <!--
     Package metadata that is identical across the three shipping packages. Everything that
     differs per package — PackageId, AssemblyName, Description, project references — stays in