Skip to content

ci(pack): enable PackageValidation with baseline v0.4.1 (post-deploy baseline bump) - #319

Merged
Chris-Wolfgang merged 1 commit into
mainfrom
claude/enable-package-validation
Aug 20, 2026
Merged

Chris-Wolfgang merged 1 commit into
mainfrom
claude/enable-package-validation

Conversation

@Chris-Wolfgang

Copy link
Copy Markdown
Owner

Summary

Post-deploy baseline bump for the v0.4.1 release just shipped. 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.

Change

src/Wolfgang.TryPattern/Wolfgang.TryPattern.csproj:

<EnablePackageValidation>true</EnablePackageValidation>
<PackageValidationBaselineVersion>0.4.1</PackageValidationBaselineVersion>

Plus a <!-- ... --> comment above explaining the mechanism, the maintenance step (bump this baseline on every release), and the relationship to api-compat.yaml (which already runs the same validation dynamically on PRs).

Why this + api-compat.yaml both

api-compat.yaml runs ApiCompat against the latest-published NuGet version dynamically — great for catching breaks on PRs, before the release. PackageValidationBaselineVersion runs the same validation at pack time, so the check also runs inside release.yaml's `pack-and-validate` job (belt + suspenders — if a PR somehow slips through without triggering api-compat.yaml, this still catches it at release).

Maintenance step this institutes

Every future release should bump <PackageValidationBaselineVersion> to whatever version just shipped, as a post-deploy PR. That's the "post-deploy baseline bump" step in the per-repo release flow. This PR is the first application of it (there was no baseline in the csproj before).

Test plan

  • Verified locally: dotnet pack -c Release on Wolfgang.TryPattern.csproj builds all 4 TFMs and packs Wolfgang.TryPattern.0.4.1.{nupkg,snupkg} with package validation clean. The v0.4.1-vs-v0.4.1 comparison is a no-op ABI diff by construction; the mechanism is live and will catch real breaks on the NEXT release's pack.
  • CI: standard pr.yaml Stage 1/2/3 + SourceLink + AOT smoke + ApiCompat green.
  • After merge: next PATCH release (whenever it ships) will bump this value again.

Refs: #309, #317

🤖 Generated with Claude Code

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>
Copilot AI lite review requested due to automatic review settings August 20, 2026 17:08

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@github-actions

Copy link
Copy Markdown
Contributor

PR benchmarks vs base (bc20979)

Thresholds: time > +20% or allocations > +50% trigger a gate failure (label perf-impact-acknowledged overrides).

Benchmark Δ time Δ alloc
Action_Success +0.3% 0 (new)
Action_WithException -0.9% +0.0%
RunAsync_Action_Success -1.7% -0.1%
RunAsync_Action_WithException -5.9% +0.0%
RunAsync_Func_Success +3.5% +0.0%
RunAsync_Func_WithException -0.1% +0.0%
Run_Func_Success -3.4% +0.0%
Run_Func_WithException -0.4% +0.0%

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants