Skip to content

Dispose with ConfigureAwait(false) in the procedure-name queries; pin Pkcs in the benchmarks - #108

Merged
electricessence merged 2 commits into
masterfrom
fix/configure-await-dispose
Nov 10, 2026
Merged

electricessence merged 2 commits into
masterfrom
fix/configure-await-dispose

Conversation

@electricessence

Copy link
Copy Markdown
Collaborator

What changes

The procedure-name query in Source/SqlClient/ExpressiveSqlCommand.cs and Source/MSSqlClient/ExpressiveSqlCommand.cs used await using on the command and reader, which awaits DisposeAsync without ConfigureAwait(false). They now use await using var commandDisposal = command.ConfigureAwait(false); and the same for the reader, the form the rest of these packages use. Disposal order is unchanged (reader before command). No other await using in Source lacked it.

The benchmarks project references Microsoft.Data.SqlClient 7.1.1, which brings System.Security.Cryptography.Pkcs 9.0.18 (NU1902/NU1903, GHSA-846f-f764-76mx and GHSA-2fmv-rv2c-59x7). It now pins 10.0.14, as Source/MSSqlClient already does. The benchmarks are not shipped.

Checks

  • Release and Debug solution builds: 0 warnings, 0 errors.
  • Core tests: 9255 passed in Release and in Debug.
  • Samples: 96 of 96 checks passed.
  • dotnet format style and analyzers at info severity, all 9 projects: 0 findings.
  • DocFX: 0 warnings, 0 errors.
  • dotnet list package --vulnerable --include-transitive on the benchmarks project: no vulnerable packages.

🤖 Generated with Claude Code

electricessence and others added 2 commits November 9, 2026 23:10
… their command and reader with ConfigureAwait(false), like every other await in the library.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…, so Microsoft.Data.SqlClient no longer brings in the vulnerable 9.0.18.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@electricessence
electricessence merged commit a0dcffd into master Nov 10, 2026
2 checks passed
@electricessence
electricessence deleted the fix/configure-await-dispose branch November 10, 2026 07:18
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