Validate installed SqlClient family versions from Logging packages

[paulmedynski]

Description

Ship exact installed-family package validation from Internal.Logging, in both build/ and buildTransitive/.

• Use the resolved Logging package version as the anchor; check only installed SqlClient, Abstractions, Azure and AKV family members.
• Collect compile/reference/runtime/RID-specific assets safely when references lack NuGet metadata.
• Support PackageReference and legacy packages.config, including prerelease labels, SQLCLIENT001 diagnostics, design-time skipping and the emergency SqlClientEnforceFamilyVersions=false opt-out.
• Exclude independently versioned SqlServer.Server and native SNI packages.
• Document scope and escape hatch. Ordinary project references do not propagate these consumer build assets.

Layer 1 of 6 in the seven-PR phase-one authentication stack; based on the branch-guidance layer. No authentication implementation changes.

Issues

No issue is automatically closed by this infrastructure layer.

Testing

• pwsh -NoProfile -File src/Microsoft.Data.SqlClient.Internal/Logging/test/RunVersionChecks.ps1 — passed, 503 checked dotnet commands.
  • Synthetic exact-version matrix covers all asset groups, metadata-free references, stable/prerelease versions, optional packages, exclusions, design-time skipping, opt-out and packages.config.
  • The real Logging package contains identical build/ and buildTransitive/ targets.
  • Actual isolated direct/transitive NuGet consumers prove automatic imports, matching/mixed versions and runtime-only dependencies. Other family packages are small fixtures, not production builds.
• git -C ../phase-1.1 diff --check — passed before commit.

No SQL Server or identity service was required.

Guidelines

Please review the contribution guidelines before submitting a pull request:

• Contributing

• Code of Conduct

• Best Practices

• Coding Style

• Review Process

• Tests added or updated.

• Public API changes documented — no public API changes.

• Verified against customer repro — no customer repro applies.

• Ensure no breaking changes introduced — mixed installed family versions intentionally fail with an explicit emergency opt-out.

[Copilot]

🟡 Changes recommended

Project-specific legacy packages configuration files currently bypass validation.

2 open findings

• Support project-specific packages.config filenames · New
• Add repository license header to shipped targets file · New

What changed in this PR

Adds consumer-side validation ensuring installed SqlClient family packages use identical versions.

Changes:

• Ships validation through build/ and buildTransitive/.
• Adds extensive synthetic and package-consumer tests.
• Documents diagnostics and the emergency opt-out.

File	Description
BUILDGUIDE.md	Documents validation and testing.
Logging.targets	Implements family-version checks.
Logging.csproj	Packages the targets.
PackageReadme.md	Documents consumer behavior.
RunVersionChecks.ps1	Adds the regression matrix.

🧠 Review effort: Balanced

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (dev/paul/aot/phase-1.0@c3f01b0). Learn more about missing BASE report.

Additional details and impacted files

@@                    Coverage Diff                    @@
##             dev/paul/aot/phase-1.0    #4815   +/-   ##
=========================================================
  Coverage                          ?   65.10%           
=========================================================
  Files                             ?      286           
  Lines                             ?    68600           
  Branches                          ?        0           
=========================================================
  Hits                              ?    44665           
  Misses                            ?    23935           
  Partials                          ?        0           

Flag	Coverage Δ
PR-SqlClient-Project	65.10% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.