Skip to content

Move SqlClient to 6.1.8, and drop the Pkcs pin it no longer needs - #3

Merged
sadeqabuhattem merged 1 commit into
mainfrom
chore/sqlclient-6.1.8
Nov 14, 2026
Merged

sadeqabuhattem merged 1 commit into
mainfrom
chore/sqlclient-6.1.8

Conversation

@sadeqabuhattem

Copy link
Copy Markdown
Member

What

Moves Microsoft.Data.SqlClient from 6.1.6 to 6.1.8, and removes the
System.Security.Cryptography.Pkcs pin that 6.1.6 needed.

Why

SqlClient 6.1.6 brought in Pkcs 9.0.11, which has two advisories
(GHSA-846f-f764-76mx, GHSA-2fmv-rv2c-59x7), so Directory.Packages.props pinned Pkcs forward to
10.0.13. SqlClient 6.1.8 brings in Pkcs 9.0.21, past both, so the pin has nothing left to do.

SqlClient is referenced only by the integration tests (the Dapper store's SQL Server suite). No
shipped package depends on it.

Verified locally

  • dotnet restore --force-evaluate (fresh vulnerability data): clean.
  • The integration tests now resolve SqlClient 6.1.8 and Pkcs 9.0.21; dotnet list package --vulnerable --include-transitive finds none.
  • Release build of the whole solution: 0 warnings, 0 errors.
  • Tests in Release: UnitTests 189, ProviderTests 238, ApiTests 59, SurfaceTests 7 (each on net8.0
    and net10.0), IntegrationTests 202 against PostgreSQL, SQL Server and MongoDB. All pass.

🤖 Generated with Claude Code

6.1.8 brings in System.Security.Cryptography.Pkcs 9.0.21, past both
advisories the pin was there for, so NuGet audit stays clean without it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sadeqabuhattem
sadeqabuhattem merged commit 9830aed into main Nov 14, 2026
5 checks passed
@sadeqabuhattem
sadeqabuhattem deleted the chore/sqlclient-6.1.8 branch November 14, 2026 19:26
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.

1 participant