Skip to content

chore(deps): update dependency microsoft.data.sqlclient to 7.0.2#150

Open
devlead wants to merge 1 commit into
mainfrom
renovate/microsoft.data.sqlclient-7.x
Open

chore(deps): update dependency microsoft.data.sqlclient to 7.0.2#150
devlead wants to merge 1 commit into
mainfrom
renovate/microsoft.data.sqlclient-7.x

Conversation

@devlead

@devlead devlead commented Jun 26, 2026

Copy link
Copy Markdown
Member

This PR contains the following updates:

Package Type Update Change
Microsoft.Data.SqlClient (source) nuget patch 7.0.17.0.2

Release Notes

dotnet/sqlclient (Microsoft.Data.SqlClient)

v7.0.2

This update brings the following changes since the 7.0.1 release.
See the full release notes for detailed descriptions.

Important — package version alignment: Starting with 7.0.2, the Microsoft.Data.SqlClient driver and its companion packages share a single aligned version. The following packages now ship together as 7.0.2:

  • Microsoft.Data.SqlClient
  • Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider
  • Microsoft.Data.SqlClient.Extensions.Azure
  • Microsoft.Data.SqlClient.Extensions.Abstractions
  • Microsoft.Data.SqlClient.Internal.Logging

(Microsoft.SqlServer.Server continues to version independently and remains at 1.0.0.)

Applications must reference the same versions of Microsoft.Data.SqlClient and its extensions for best compatibility. In particular, applications that reference Microsoft.Data.SqlClient.Extensions.Azure must upgrade it to 7.0.2 when upgrading Microsoft.Data.SqlClient to 7.0.2.

Breaking change (.NET Framework only): As part of this alignment, the AssemblyVersion of Microsoft.Data.SqlClient.Extensions.Azure, Microsoft.Data.SqlClient.Extensions.Abstractions, and Microsoft.Data.SqlClient.Internal.Logging changed from 1.0.0.0 to 7.0.0.0. On .NET Framework, AssemblyVersion is part of the strong-name identity, so applications that drop these assemblies into an existing deployment without rebuilding must rebuild against the 7.0.2 packages (or add binding redirects). Applications on .NET / .NET Core are not affected. Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider already used a 7.x assembly version and is unaffected.

Fixed
  • Fixed a NullReferenceException in SqlCommand.Cancel() when the active connection has already been torn down.
    (#​4372,
    #​4373)

  • Fixed a NullReferenceException in SqlDataReader.GetBytes/GetChars when called with a null destination buffer.
    (#​4159,
    #​4206)

  • Fixed Always Encrypted column master key signature verification incorrectly reusing cached results.
    (#​4339,
    #​4343)

Changed
  • Hardened TDS token parsing by adding data-length bounds checks for token and feature-extension-acknowledgment data.
    (#​4340,
    #​4358)

  • Released Microsoft.Data.SqlClient.Extensions.Azure 7.0.2, adding WAM broker support for Entra ID authentication modes on Windows. See release notes.
    (#​4288,
    #​4388)

  • Re-shipped Microsoft.Data.SqlClient.AlwaysEncrypted.AzureKeyVaultProvider, Microsoft.Data.SqlClient.Extensions.Abstractions, and Microsoft.Data.SqlClient.Internal.Logging as 7.0.2 (version alignment only, no functional changes). See release notes for AKV, Abstractions, and Logging.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

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