Skip to content

ci(pack): enable PackageValidation with per-package baselines (#175) #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Chris-Wolfgang merged 1 commit into from
Aug 21, 2026
Merged

ci(pack): enable PackageValidation with per-package baselines (#175) #190

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions ...ns.Logging.Data.EntityFramework6/Wolfgang.Extensions.Logging.Data.EntityFramework6.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,17 @@
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, dropped TFMs)
fail pack instead of shipping. release.yaml's pack-and-validate
job exercises this at release time. Baseline must be bumped to
the newest published version after every release — that's the
"post-deploy baseline bump PR" step in the per-repo release flow.
EF6 lags the main package's cadence — baseline is the last EF6
release (0.2.0), not the current Data release. -->
<EnablePackageValidation>true</EnablePackageValidation>
<PackageValidationBaselineVersion>0.2.0</PackageValidationBaselineVersion>
<Title>$(AssemblyName)</Title>
<Description>Passive structured logging of every Entity Framework 6 command, connection, and transaction event via the EF6 interceptor pipeline. Register once at startup with AddLoggingInterceptors; delegates to Wolfgang.Extensions.Logging.Data for rendering and secret redaction.</Description>
<PackageProjectUrl>https://github.com/Chris-Wolfgang/Extensions-Logging-Data</PackageProjectUrl>
Expand Down
9 changes: 9 additions & 0 deletions src/Wolfgang.Extensions.Logging.Data/Wolfgang.Extensions.Logging.Data.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,15 @@
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, dropped TFMs)
fail pack instead of shipping. release.yaml's pack-and-validate
job exercises this at release time. Baseline must be bumped to
the newest published version after every release — that's the
"post-deploy baseline bump PR" step in the per-repo release flow. -->
<EnablePackageValidation>true</EnablePackageValidation>
<PackageValidationBaselineVersion>0.3.0</PackageValidationBaselineVersion>
<Title>$(AssemblyName)</Title>
<Description>Extension methods for ILogger and ILogger&lt;T&gt; that log DbConnection, DbCommand, DbParameter, and DbParameterCollection from System.Data.Common, with built-in secret redaction (passwords in connection strings, configurable parameter values).</Description>
<PackageProjectUrl>https://github.com/Chris-Wolfgang/Extensions-Logging-Data</PackageProjectUrl>
Expand Down