[dependabot]

⚠️ Dependabot is rebasing this PR ⚠️

Rebasing might not happen immediately, so don't worry if this takes some time.

Note: if you make any changes to this PR yourself, they will take precedence over the rebase.

---

Updated Microsoft.AspNetCore.OpenApi from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Data.SqlClient from 6.0.1 to 6.1.8.

Release notes

Sourced from Microsoft.Data.SqlClient's releases.

6.1.8

This update brings the following changes since the 6.1.7 release:

Changed

• Updated the System.Security.Cryptography.Pkcs dependency to 8.0.2 (was 8.0.1) for .NET Framework 4.6.2, .NET 8.0, and .NET Standard 2.0, and updated the Microsoft.Extensions.Caching.Memory, System.Configuration.ConfigurationManager, and System.Security.Cryptography.Pkcs dependencies to 9.0.21 (was 9.0.11) for .NET 9.0.
  (#​4842, #​4862, #​4870)

• Improved the error reported when Active Directory Interactive authentication through the Windows Web Account Manager (WAM) broker fails because the host has no parent window, such as a service or Azure Functions host. The resulting error now explains the supported alternatives: supply a parent window with SetParentActivityOrWindowFunc, use Active Directory Default with a configured non-interactive credential, or supply a custom ApplicationClientId with UseWamBroker disabled. The original MSAL error code and inner exception are preserved, and authentication selection, retry behavior, and other failures are unchanged. (Windows only)
  (#​4854, #​4858, #​4918)

Fixed

• Fixed the managed SNI path ignoring HostNameInCertificate during server certificate validation. When HostNameInCertificate is set, it is now the only host name the server certificate is validated against, and certificates that do not match it are rejected. Default host-name selection when the property is not set, certificate chain validation, ServerCertificate matching, and the connection destination are unchanged. (net8.0/net9.0 only)
  (#​4905, #​4909)

• Fixed Always Encrypted enclave session caching so that cached enclave sessions are isolated by attestation protocol. A session established with one Attestation Protocol setting is no longer reused by a connection to the same server, database, and attestation URL that uses a different protocol.
  (#​4829, #​4868)

• Fixed SqlDataReader.HasRows returning false when a result set contains rows but the server sends multiple informational messages, or an informational message before an ORDER token, ahead of the first row. Empty results still report false, and InfoMessage delivery is unchanged.
  (#​3018, #​4773, #​4898)

• Fixed an intermittent InvalidOperationException ("Nullable object must have a value") from statistics bookkeeping when commands complete concurrently on a MARS connection. This issue was reported as a regression starting with 6.1.4.
  (#​4778, #​4875, #​4896)

• Fixed Entra ID authentication when the server supplies an authority URL with an OAuth endpoint suffix, such as https://login.microsoftonline.com/<tenant>/oauth2/authorize returned by the Dataverse/Dynamics 365 TDS endpoint. The provider now extracts the tenant from the first path segment and uses the normalized authority for Azure.Identity credentials, MSAL, and their cache keys. An authority URL that cannot be parsed now fails with a clear, localized ArgumentException naming the authority. Bare tenant authority URLs used by Azure SQL and Fabric retain their existing behavior.
  (#​4496, #​4521, #​4791, #​4807)

Target Platform Support

• .NET Framework 4.6.2+ (Windows x86, Windows x64, Windows ARM64)
• .NET 8.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)
• .NET Standard 2.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)

Full details: release-notes/6.1/6.1.8.md

6.1.7

This update brings the following changes since the 6.1.6 release:

Changed

• Updated the Microsoft.Data.SqlClient.SNI and Microsoft.Data.SqlClient.SNI.runtime dependencies to 6.0.3 (was 6.0.2).
  (#​4598)

Fixed

• Fixed ServerCertificate validation on the managed SNI path so the configured certificate is compared against the server certificate even when the server certificate passes chain and host-name validation. When certificate validation is enabled, a missing, unreadable, or invalid certificate file, a certificate mismatch, or a missing server certificate now causes the TLS handshake to fail instead of bypassing the configured certificate check. (net8.0/net9.0 only)
  (#​4445, #​4584)

• Fixed Always Encrypted VSM/HGS enclave attestation to verify that the enclave public key used to establish a session matches the key committed to by the signed attestation report. Missing, malformed, or mismatched key-binding data now causes attestation to fail before the session secret is derived.
  (#​4532, #​4552)

• Fixed SqlConnection.AccessTokenCallback not disabling Transparent Network IP Resolution by default, making it consistent with SqlConnection.AccessToken. An explicitly configured TransparentNetworkIPResolution connection-string value still takes precedence. (net462 only)
  (#​4520, #​4560)

• Fixed token authentication state handling so clearing SqlConnection.AccessToken preserves an existing AccessTokenCallback in the connection pool key, and clearing AccessTokenCallback preserves an existing AccessToken. Callback-based authentication now also follows the same prelogin server-certificate validation rules as an explicitly supplied access token.
  (#​4520, #​4560)

• Fixed configurable retry logic installing a permanent, process-wide assembly-resolution handler that could interfere with unrelated assembly loading. The handler is now active only while an explicitly configured custom retry provider is resolved and constructed, and probes AppContext.BaseDirectory instead of the current working directory. Place custom retry assemblies in the application base directory; dependencies loaded after provider construction must be resolvable through normal application dependency resolution or an application-provided handler. (net8.0/net9.0 only)
  (#​2214, #​4547, #​4664)

Target Platform Support

• .NET Framework 4.6.2+ (Windows x86, Windows x64, Windows ARM64)
• .NET 8.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)
• .NET Standard 2.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)

Full details: release-notes/6.1/6.1.7.md

6.1.6

This update brings the following changes since the 6.1.5 release:

Added

WAM broker support for the supported Entra ID authentication modes (Windows only)

What Changed:

• Added support for the Web Account Manager (WAM) broker for the supported Microsoft Entra ID authentication modes. A new ActiveDirectoryAuthenticationProviderOptions options bag and a corresponding ActiveDirectoryAuthenticationProvider(ActiveDirectoryAuthenticationProviderOptions options) constructor were introduced, exposing a UseWamBroker property (alongside ApplicationClientId and DeviceCodeFlowCallback).
  (#​4288, #​4387)
• Added a cross-platform SetParentActivityOrWindowFunc(Func<object> parentActivityOrWindowFunc) method so callers can supply a parent window handle on Windows or a parent Activity/UIViewController on Android/iOS/MAUI.

Who Benefits:

• Applications using ActiveDirectoryInteractive and other supported Entra ID authentication modes on Windows benefit from the WAM broker's improved security (tokens are brokered by the OS), single sign-on with the logged-in Windows account, and support for Conditional Access and Windows Hello.

Impact:

• When you supply your ApplicationClientId, WAM is opt-in via ActiveDirectoryAuthenticationProviderOptions.UseWamBroker. Consider enabling it when you want OS-brokered tokens, single sign-on with the signed-in Windows account, Windows Hello, and Conditional Access support.
• UseWamBroker is a Windows-only setting and has no effect on non-Windows platforms, where interactive Entra ID flows always use the system browser.
• Prefer the new options-bag constructor over the positional-argument overloads in new code.

var options = new ActiveDirectoryAuthenticationProviderOptions
{
    ApplicationClientId = "<your-app-client-id>",
    // Enable WAM (Windows only) for OS-brokered tokens, SSO, Windows Hello, and Conditional Access.
    UseWamBroker = true,
};
var provider = new ActiveDirectoryAuthenticationProvider(options);
// Supply the parent window/activity that owns the interactive sign-in prompt.
provider.SetParentActivityOrWindowFunc(() => parentWindowHandle);
SqlAuthenticationProvider.SetProvider(SqlAuthenticationMethod.ActiveDirectoryInteractive, provider);

Changed

Hardened TDS token parsing with data-length bounds checks

What Changed:

• Added bounds checking when parsing TDS token data lengths. The parser now validates the declared length of incoming token data against the available buffer before reading, rejecting malformed or out-of-range length values instead of reading past the intended boundary.
  (#​4340, #​4359)

Who Benefits:

• All consumers benefit from improved resilience against malformed or hostile TDS responses. A server (or man-in-the-middle) sending an invalid token length can no longer drive the parser to read beyond the declared payload.

Impact:
... (truncated)

6.1.5

This update brings the following changes since the 6.1.4 release:

Fixed

• Fixed a connection performance regression where SPN (Service Principal Name) generation was triggered for non-integrated authentication modes (e.g., SQL authentication) on the native SNI path, causing unnecessary DNS lookups and significantly slower connection times. Only affects .NET on Windows (not .NET Framework). (#​3523, #​3946)
• Fixed ExecuteScalar to properly propagate errors when the server sends data followed by an error token. Previously, errors such as conversion failures during WHERE clause evaluation were silently consumed during SqlDataReader.Close() instead of being thrown to the caller, which could result in transactions being unexpectedly zombied. (#​3736, #​3947)
• Fixed SqlDataReader.GetFieldType and SqlDataReader.GetProviderSpecificFieldType to return the correct type (SqlVector<float>) for vector float32 columns. Previously, these methods did not follow the same type-resolution logic as GetValue, returning an incorrect type for vector columns. (#​4104, #​4151)

Target Platform Support

• .NET Framework 4.6.2+ (Windows x86, Windows x64, Windows ARM64)
• .NET 8.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)
• .NET Standard 2.0+ (Windows x86, Windows x64, Windows ARM64, Linux, macOS)

Dependencies

.NET Framework 4.6.2

• Azure.Core 1.50.0
• Azure.Identity 1.17.1
• Microsoft.Data.SqlClient.SNI 6.0.2
• Microsoft.Extensions.Caching.Memory 8.0.1
• Microsoft.Identity.Client 4.80.0
• Microsoft.IdentityModel.JsonWebTokens 7.7.1
• Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
• System.Buffers 4.6.1
• System.Data.Common 4.3.0
• System.Diagnostics.DiagnosticSource 8.0.1
• System.IdentityModel.Tokens.Jwt 7.7.1
• System.Memory 4.6.3
• System.Security.Cryptography.Pkcs 8.0.1
• System.Text.Json 8.0.6
• System.Text.RegularExpressions 4.3.1

.NET 8.0

• Azure.Core 1.50.0
• Azure.Identity 1.17.1
• Microsoft.Data.SqlClient.SNI.runtime 6.0.2
• Microsoft.Extensions.Caching.Memory 8.0.1
• Microsoft.Identity.Client 4.80.0
• Microsoft.IdentityModel.JsonWebTokens 7.7.1
• Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
• Microsoft.SqlServer.Server 1.0.0
• System.Configuration.ConfigurationManager 8.0.1
• System.Diagnostics.DiagnosticSource 8.0.1
• System.IdentityModel.Tokens.Jwt 7.7.1
• System.Security.Cryptography.Pkcs 8.0.1

.NET 9.0

... (truncated)

6.1.4

This update brings the following changes since the 6.1.3 release:

Fixed

• Fixed NullReferenceException issue with SqlDataAdapter when processing batch scenarios where certain SQL RPC calls may not include system parameters.
  (#​3877)
• Fixed connection pooling issue where extra connection deactivation was causing active connection counts to go negative.
  (#​3776)

Added

AppContext Switch for enabling MultiSubnetFailover

What Changed:

• Added new AppContext switch Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault to set MultiSubnetFailover=true by default in connection string.
  (#​3851)

Who Benefits:

• Applications that need MultiSubnetFailover enabled globally without modifying connection strings.

Impact:

• Applications can now enable MultiSubnetFailover globally using one of the following methods:

// In application code
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault", true);

// In runtimeconfig.json
{
  "configProperties": {
    "Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault": true
  }
}

<!-- In App.Config -->
<runtime>
  <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault=true" />
</runtime>

Changed

• Optimized SqlStatistics execution timing by using Environment.TickCount instead of more expensive timing mechanisms.
  ... (truncated)

6.1.3

This update includes the following changes since the 6.1.2 release:

Added

App Context Switch for Ignoring Server-Provided Failover Partner

What Changed:

• A new app context switch Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR #​3702.

Who Benefits:

• Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
• Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.

Impact:

• If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:

AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);

• Then, ensure your connection string includes your preferred failover partner (with correct tcp:host,port) so that the client uses that instead of the server's suggestion.
• Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.

Fixed

• Fixed an issue to ensure reliable metrics initialization during startup, preventing missed telemetry when EventSource is enabled early. (#​3718)

Target Platform Support

• .NET Framework 4.6.2+ (Windows ARM64, Windows x86, Windows x64)
• .NET 8.0+ (Windows x86, Windows x64, Windows ARM64, Windows ARM, Linux, macOS)

Dependencies

.NET Framework 4.6.2+

• Azure.Core 1.47.1
• Azure.Identity 1.14.2
• Microsoft.Bcl.Cryptography 8.0.0
• Microsoft.Data.SqlClient.SNI 6.0.2
• Microsoft.Extensions.Caching.Memory 8.0.1
• Microsoft.IdentityModel.JsonWebTokens 7.7.1
• Microsoft.IdentityModel.Protocols.OpenIdConnect 7.7.1
• System.Buffers 4.5.1
• System.Data.Common 4.3.0
• System.Security.Cryptography.Pkcs 8.0.1
• System.Text.Encodings.Web 8.0.0
  ... (truncated)

6.1.2

This update brings the below changes over the previous stable release:

Fixed

• Fixed an issue where initializing PerformanceCounters would throw System.InvalidOperationException #​3629
• Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. #​3651
• Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. #​3653

6.1.1

This update includes the following changes since the 6.1.0 release:

Fixed

• Reverted changes related to improving partial packet detection, fixup, and replay functionality. This revert addresses regressions introduced in 6.1.0. (#​3556)
• Applied reference assembly corrections supporting vector, fixed JSON tests, and ensured related tests are enabled. #​3562
• Fixed SqlVector<T>.Null API signature in Reference assembly. #​3521

Changed

• Upgraded Azure.Identity and other dependencies to newer versions. (#​3538) (#​3552)

6.1.0

Release Notes

[!WARNING]
This release version is delisted from NuGet.org and is no longer supported.
It contains critical bugs that make it unsuitable for use.

Stable Release 6.1.0 - 2025-07-25

This update brings the following changes since the 6.0.2 stable release:

Added

Added dedicated SQL Server vector datatype support

What Changed:

• Optimized vector communications between MDS and SQL Server 2025, employing a custom binary format over the TDS protocol. (#​3433, #​3443)
• Reduced processing load compared to existing JSON-based vector support.
• Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

• Applications moving large vector data sets will see beneficial improvements to processing times and memory requirements.
• Vector-specific APIs are ready to support future numeric representations with a consistent look-and-feel.

Impact:

• Reduced transmission and processing times for vector operations versus JSON using SQL Server 2025 preview:
  • Reads: 50x improvement
  • Writes: 3.3x improvement
  • Bulk Copy: 19x improvement
  • (Observed with vector column of max 1998 size, and 10,000 records for each operation.)
• Improved memory footprint due to the elimination of JSON serialization/deserialization and string representation bloat.
• For backwards compatibility with earlier SQL Server Vector implementations, applications may continue to use JSON strings to send/receive vector data, although they will not see any of the performance improvements noted above.

Revived .NET Standard 2.0 target support

What Changed:

• Support for targeting .NET Standard 2.0 has returned. (#​3381)
• Support had previously been removed in the 6.0 release, with the community voicing concerns.

Who Benefits:

• Libraries that depend on MDS may seamlessly target any of the following frameworks:
  • .NET Standard 2.0
  • .NET Framework 4.6.2 and above
  • .NET 8.0
  • .NET 9.0
• Applications should continue to target runtimes.
  ... (truncated)

6.1.0-preview2

Preview Release 6.1.0-preview2.25178.5 - 2025-06-27

This update brings the following changes since the 6.1.0-preview1 release:

Added

Added dedicated SQL Server vector datatype support

What Changed:

• Optimized vector communications between MDS and SQL Server 2025, employing a custom binary format over the TDS protocol. (#​3433, #​3443)
• Reduced processing load compared to existing JSON-based vector support.
• Initial support for 32-bit single-precision floating point vectors.

Who Benefits:

• Applications moving large vector data sets will see beneficial improvements to processing times and memory requirements.
• Vector-specific APIs are ready to support future numeric representations with a consistent look-and-feel.

Impact:

• Reduced transmission and processing times for vector operations versus JSON using SQL Server 2025 preview:
  • Reads: 50x improvement
  • Writes: 3.3x improvement
  • Bulk Copy: 19x improvement
  • (Observed with vector column of max 1998 size, and 10,000 records for each operation.)
• Improved memory footprint due to the elimination of JSON serialization/deserialization and string representation bloat.
• For backwards compatibility with earlier SQL Server Vector implementations, applications may continue to use JSON strings to send/receive vector data, although they will not see any of the performance improvements noted above.

Revived .NET Standard 2.0 target support

What Changed:

• Support for targeting .NET Standard 2.0 has returned. (#​3381)
• Support had previously been removed in the 6.0 release, with the [community voicing concerns] (Microsoft.Data.SqlClient 6.0 and .Net Standard dotnet/SqlClient#3115).

Who Benefits:

• Libraries that depend on MDS may seamlessly target any of the following frameworks:
  • .NET Standard 2.0
  • .NET Framework 4.6.2 and above
  • .NET 8.0
  • .NET 9.0
• Applications should continue to target runtimes.
  • The MDS .NET Standard 2.0 target framework support does not include an actual implementation, and cannot be used with a runtime.
  • An application's build/publish process should always pick the appropriate MDS .NET/.NET Framework runtime implementation.
  • Custom build/publish actions that incorrectly try to deploy the MDS .NET Standard 2.0 reference DLL at runtime are not supported.

Impact:

... (truncated)

6.1.0-preview1

This update brings the following changes over the previous release:

Added

• Added packet multiplexing support to improve large data read performance. #​2714 #​3161 #​3202
• Added support for special casing with Fabric endpoints. #​3084

Fixed

• Fixed distributed transactions to be preserved during pooled connection resets. #​3019.
• Fixed application crash when the Data Source parameter begins with a comma. #​3250.
• Resolved synonym count discrepancies in debug mode. #​3098.
• Addressed warnings for down-level SSL/TLS versions. #​3126.

Changed

• Optimized binary size for AOT. #​3091
• Refined bulk copy operations to handle unmatched column names more effectively. #​3205.
• Enhanced SqlBulkCopy to explicitly identify mismatched column names. #​3183.
• Optimized outgoing SSPI blob handling using IBufferWriter<byte>. #​2452.
• Replaced byte[] with string for SNI to improve efficiency. #​2790.
• Code cleanup to remove SQL 2000 support #​2839, #​3206, #​3217,
• Connection pool design refactor for a modular connection pool design #​3199
• Updated various dependencies #​3229, primarily:
  • System.Text.Encodings.Web to v8.0.0
  • System.Text.Json to v8.0.5
  • Azure.Identity to v1.13.2
  • Microsoft.Identity.Model.Json.Web.Tokens to v7.7.1
  • Microsoft.Identity.Model.Protocols.OpenIdConnect to v7.7.1
• Code merge towards a unified SqlClient project, aligning .NET Framework and .NET Core implementations. (#​2957, #​2963, #​2984, #​2982, #​3023, #​3015, #​2967, #​3164, #​3163, #​3171, #​3182, #​3179, #​3156, #​3213, #​3232, #​3236, #​3231, #​3241, #​3246, #​3247, #​3222, #​3255, #​3254, #​3259, #​3264, #​3256, #​3251, #​3275, #​3277, #​3263, #​3292, #​3208).
• Test improvements include updates to test references, removal of hardcoded certificates, improved stability, and better coverage (#​3041, #​3034, #​3130, #​3128, #​3181, #​3060, #​3184, #​3033, #​3186, #​3025, #​3230, #​3237, #​3059, #​3061).

New Contributors

• @​emmanuel-ferdman made their first contribution in Update DockerLinuxTest/Program.cs reference dotnet/SqlClient#3041
• @​MaceWindu made their first contribution in Fix typo in Update 6.0.0-preview1.md dotnet/SqlClient#3134
• @​JNjenga made their first contribution in SqlBulkCopy: Explicitly state column name that mismatches(#3170) dotnet/SqlClient#3183
• @​Midhunnnk made their first contribution in Fix crash when Data Source starts with a comma dotnet/SqlClient#3250

6.0.5

[Stable release 6.0.5] - 2026-01-15

This update brings the below changes over the previous stable release:

Fixed

• Fixed NullReferenceException issue with SqlDataAdapter when processing batch scenarios where certain SQL RPC calls may not include system parameters.
  (#​3878)

Added

What Changed:

• Added new AppContext switch Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault to set MultiSubnetFailover=true by default in connection string.
  (#​3852)

Who Benefits:

• Applications that need MultiSubnetFailover enabled globally without modifying connection strings.

Impact:

• Applications can now enable MultiSubnetFailover globally using one of the following methods:

// In application code
AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault", true);

// In runtimeconfig.json
{
  "configProperties": {
    "Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault": true
  }
}

<!-- In App.Config -->
<runtime>
  <AppContextSwitchOverrides value="Switch.Microsoft.Data.SqlClient.EnableMultiSubnetFailoverByDefault=true" />
</runtime>

Changed

• Updated dependencies (#​3840):
  • .NET Framework 4.6.2:

... (truncated)

6.0.4

This update brings the below changes over the 6.0.3 release:

Added

App Context Switch for Ignoring Server-Provided Failover Partner

What Changed:

• A new app context switch Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner was introduced to let the client ignore server-provided failover partner info in Basic Availability Groups (BAGs). When the switch is enabled, only the failover partner specified in the connection string is used; server-supplied partner values are skipped. This context switch was introduced in PR #​3703.

Who Benefits:

• Applications connecting to SQL Server BAGs using TCP and custom ports, especially where the server's provided partner name lacks the protocol, host, or port. This avoids connection failures when the server-provided partner is incompatible or incomplete.
• Teams who manage availability groups and rely on client-side control of failover behavior in heterogeneous networking environments.

Impact:

• If your environment might be affected (i.e., you operate a BAG with custom ports, or have experienced failures after failover), you can enable the new switch in your application:

AppContext.SetSwitch("Switch.Microsoft.Data.SqlClient.IgnoreServerProvidedFailoverPartner", true);

• Then, ensure your connection string includes your preferred failover partner (with correct tcp:host,port) so that the client uses that instead of the server's suggestion.
• Without enabling this, by default, the client continues to prefer the server-provided partner, maintaining backwards compatibility.

Target Platform Support

• .NET Framework 4.6.2+ (Windows ARM64, Windows x64, Windows x86)
• .NET 8.0+ (Linux, macOS, Windows ARM64, Windows x64, Windows x86)

Dependencies

.NET Framework

• Azure.Identity 1.14.2
• Microsoft.Bcl.Cryptography 8.0.0
• Microsoft.Data.SqlClient.SNI 6.0.2
• Microsoft.Extensions.Caching.Memory 8.0.1
• Microsoft.IdentityModel.JsonWebTokens 7.5.0
• Microsoft.IdentityModel.Protocols.OpenIdConnect 7.5.0
• System.Buffers 4.5.1
• System.Security.Cryptography.Pkcs 8.0.1
• System.Text.Encodings.Web 8.0.0
• System.Text.Json 8.0.5
• System.Data.Common 4.3.0

.NET 8

• Azure.Identity 1.14.2
  ... (truncated)

6.0.3

This update brings the below changes over the previous stable release:

Fixed

• Fixed an issue where a Custom SqlClientAuthenticationProvider was being overwritten by default implementation. #​3652
• Fixed a concurrency issue in connection pooling where the number of active connections could be lower than the configured maximum pool size. #​3654

Changed

• Updated MSAL usage as per code compliance requirements #​3360
• Updated SqlDecimal implementation to improve code compliance #​3466
• Updated Azure.Identity and related dependencies #​3553

6.0.2

This update brings the below changes over the previous release:

Fixed

• Fixed possible NullPointerException during socket receive #​3283
• Fixed reference assembly definitions for SqlJson APIs #​3169
• Fixed an error reading the output parameter of type JSON while executing stored procedure #​3173

Changed

• Updated the below dependencies:
  • Updated Microsoft.Bcl.Cryptography from 9.0.0 to 9.0.4 for .NET 9 targeted dll. #​3281
  • Updated Microsoft.Extensions.Caching.Memory from 9.0.0 to 9.0.4 for .NET 9 targeted dll. #​3281
  • Updated System.Configuration.ConfigurationManager from 9.0.0 to 9.0.4 for .NET 9 targeted dll. #​3281
  • Updated System.Security.Cryptography.Pkcs from 9.0.0 to 9.0.4 for .NET 9 targeted dll. #​3281

Commits viewable in compare view.

Updated Microsoft.Extensions.Configuration.Abstractions from 10.0.8 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Configuration.Abstractions's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.DependencyInjection.Abstractions from 10.0.8 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Hosting from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Hosting's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Abstractions from 10.0.8 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Logging.Abstractions's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Options from 10.0.8 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Options's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Options.ConfigurationExtensions from 10.0.8 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Options.ConfigurationExtensions's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.12.0.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated System.Security.Cryptography.Pkcs from 10.0.14 to 10.0.15.

Release notes

Sourced from System.Security.Cryptography.Pkcs's releases.

No release notes found for this version range.

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions