From bc20979f5518f936b8a076cb5ca5352d6fa85ae0 Mon Sep 17 00:00:00 2001
From: Chris Wolfgang <210299580+Chris-Wolfgang@users.noreply.github.com>
Date: Thu, 20 Aug 2026 13:07:55 -0400
Subject: [PATCH] ci(pack): enable PackageValidation with baseline v0.4.1

Post-deploy baseline bump for the v0.4.1 release. Turns on
Microsoft.DotNet.ApiCompat during `dotnet pack` (both local and
release.yaml) with v0.4.1 as the baseline, so accidental ABI breaks
(removed / renamed / type-changed public members) fail pack instead of
shipping.

Complements the existing `api-compat.yaml` PR workflow, which runs the
same validation dynamically against the latest-published NuGet version.
The static baseline here catches the same breaks earlier in the release
pipeline (at pack time, which `release.yaml` runs) and is the standard
fleet post-deploy baseline-bump step.

Verified locally: `dotnet pack -c Release` builds all 4 TFMs and creates
Wolfgang.TryPattern.0.4.1.{nupkg,snupkg} with package validation clean
(v0.4.1 vs v0.4.1 baseline is a no-op ABI diff; the mechanism is live
and will catch real breaks on the NEXT release's pack).

Next release will bump this value to whatever ships (e.g. 0.4.2, 0.5.0)
as part of that release's post-deploy baseline-bump PR.

Refs: #309, #317

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
---
 src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj b/src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj
index 0baa8168..e89ad314 100644
--- a/src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj
+++ b/src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj
@@ -11,6 +11,16 @@
          the actual release version. -->
     <AssemblyVersion>1.0.0.0</AssemblyVersion>
     <FileVersion>$([System.Text.RegularExpressions.Regex]::Replace("$(Version)", "[-+].*$", "")).0</FileVersion>
+    <!-- Package validation: `dotnet pack` runs Microsoft.DotNet.ApiCompat
+         against the last-published NuGet version so accidental ABI breaks
+         (removed / renamed / type-changed public members) fail pack instead
+         of shipping. Baseline must be bumped to the newest published version
+         after every release — this is the "post-deploy baseline bump PR"
+         step in the per-repo release flow. Complements api-compat.yaml,
+         which runs the same validation dynamically on PRs; this baseline
+         catches the same breaks at pack time, which release.yaml exercises. -->
+    <EnablePackageValidation>true</EnablePackageValidation>
+    <PackageValidationBaselineVersion>0.4.1</PackageValidationBaselineVersion>
     <Title>$(AssemblyName)</Title>
     <Description>A .NET library demonstrating the Try pattern for structured error handling and result types.</Description>
     <PackageTags>try;result;error-handling;exception-handling;functional;railway-oriented;dotnet</PackageTags>