Update all non-major dependencies by renovate[bot] · Pull Request #15 · CodeLogicIncEngineering/Dapper

renovate · 2026-01-26T17:18:59Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
Azure.Identity (source)	`1.14.2` → `1.17.1`
BenchmarkDotNet	`0.14.0` → `0.15.8`
DevExpress.Xpo (source)	`24.2.3` → `24.2.13`
DuckDB.NET.Data.Full	`1.1.3` → `1.4.3`
EntityFramework (source)	`6.1.3` → `6.5.1`
FirebirdSql.Data.FirebirdClient (source)	`10.3.2` → `10.3.4`
Microsoft.Build.Traversal	`2.0.24` → `2.2.3`
Microsoft.Data.SqlClient (source)	`6.1.1` → `6.1.4`
Microsoft.EntityFrameworkCore.SqlServer (source)	`[3.1.10]` → `[3.1.32]`
Microsoft.EntityFrameworkCore.SqlServer (source)	`8.0.12` → `8.0.23`
Microsoft.NET.Test.Sdk	`17.12.0` → `17.14.1`
MySqlConnector (source)	`2.4.0` → `2.5.0`
NHibernate (source)	`5.5.2` → `5.6.0`
Nerdbank.GitVersioning	`3.7.115` → `3.9.50`
Npgsql	`8.0.6` → `8.0.8`
Npgsql	`9.0.2` → `9.0.4`
ServiceStack.OrmLite.SqlServer	`8.5.2` → `8.10.0`
System.ValueTuple	`4.5.0` → `4.6.1`
linq2db.SqlServer (source)	`5.4.1` → `5.4.1.9`
xunit.runner.visualstudio	`3.0.1` → `3.1.5`

Release Notes

Azure/azure-sdk-for-net (Azure.Identity)

`v1.17.1`

Compare Source

1.17.1 (2025-11-18)

Other Changes

Updated Microsoft.Identity.Client and Microsoft.Identity.Client.Extensions.Msal dependencies to version 4.78.0.

`v1.17.0`

Compare Source

1.17.0 (2025-10-07)

Bugs Fixed

TenantId is now configured via MSAL's WithTenantId instead of WithTenantIdFromAuthority to prevent malformed Uris to the authority.

Other Changes

Deprecated BrowserCustomizationOptions.UseEmbeddedWebView property. This option requires additional dependencies on Microsoft.Identity.Client.Desktop and is no longer supported. Consider using brokered authentication instead.

`v1.16.0`

Compare Source

1.16.0 (2025-09-09)

Features Added

Added a new DefaultAzureCredential constructor that accepts a custom environment variable name for credential configuration. This provides flexibility beyond the default AZURE_TOKEN_CREDENTIALS environment variable. The constructor accepts any environment variable name and uses the same credential selection logic as the existing AZURE_TOKEN_CREDENTIALS processing.
Added DefaultAzureCredential.DefaultEnvironmentVariableName constant property that returns "AZURE_TOKEN_CREDENTIALS" for convenience when referencing the default environment variable name.
AzureCliCredential, AzurePowerShellCredential, and AzureDeveloperCliCredential now throw an AuthenticationFailedException when the TokenRequestContext includes claims, as these credentials do not support claims challenges. The exception message includes guidance for handling such scenarios.
When AZURE_TOKEN_CREDENTIALS or the equivalent custom environment variable is configured to ManagedIdentityCredential, the DefaultAzureCredential does not issue a probe request and performs retries with exponential backoff.

Bugs Fixed

Fixed AzureDeveloperCliCredential hanging when the AZD_DEBUG environment variable is set by adding the --no-prompt flag to prevent interactive prompts (#52005).
BrokerCredential is now included in the chain when AZURE_TOKEN_CREDENTIALS is set to dev.
Fixed an issue that prevented ManagedIdentityCredential from utilizing the token cache in Workload Identity Federation environments.
Fixed a bug in DefaultAzureCredential that caused the credential chain to be constructed incorrectly when using AZURE_TOKEN_CREDENTIALS in combination with DefaultAzureCredentialOptions.

Other Changes

The BrokerCredential is now always included in the DefaultAzureCredential chain. If the Azure.Identity.Broker package is not referenced, an exception will be thrown when GetToken is called, making its behavior consistent with the rest of the credentials in the chain.
Updated Microsoft.Identity.Client dependency to version 4.76.0.
Updated Microsoft.Identity.Client.Extensions.Msal dependency to version 4.76.0.

`v1.15.0`

Compare Source

1.15.0 (2025-08-07)

Breaking Changes

Behavioral Breaking Changes

Deprecated SharedTokenCacheCredential. The supporting credential (SharedTokenCacheCredential) was a legacy mechanism for authenticating clients using credentials provided to Visual Studio. For brokered authentication, consider using InteractiveBrowserCredential instead. The following changes have been made:
- SharedTokenCacheCredential class is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
- SharedTokenCacheCredentialOptions class is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
- DefaultAzureCredentialOptions.ExcludeSharedTokenCacheCredential property is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
- SharedTokenCacheUsername property is marked as [Obsolete] and [EditorBrowsable(EditorBrowsableState.Never)]
- SharedTokenCacheCredential is no longer included in the DefaultAzureCredential authentication flow

Bugs Fixed

Tenant ID comparisons in credential options are now case-insensitive. This affects AdditionallyAllowedTenants values which will now be matched against tenant IDs without case sensitivity, making the authentication more resilient to case differences in tenant IDs returned from WWW-Authenticate challenges (#51693).

Other Changes

BrokerAuthenticationCredential has been renamed as BrokerCredential.
Added the EditorBrowsable(Never) attribute to property VisualStudioCodeTenantId as TenantId is preferred. The VisualStudioCodeTenantId property exists only to provide backwards compatibility.

dotnet/BenchmarkDotNet (BenchmarkDotNet)

Highlights

Allow override method/property for ParamsSource (#2832)

`v0.15.3`: 0.15.3

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.3.html

Highlights

Improvements:

Naot instruction set support for .NET 10+, migrate to ISA groupings in CPU summary #2828
Support benchmark filtering for TestAdapter #2662 #2788
Support non-primitive external types in ArgumentsSource #2820
Enable MSBuild parallel build via --nodeReuse:false #2693 #2814
Improve CPU detection #2747 #2749
Enable assembly signing for debug build #2774

Deprecations:

Deprecated WithNuget #2812

Bug fixes:

Fix InvalidOperationException in diagnosers #2758 #2805
Fix file detection in NativeMemoryProfiler #2794 #2795
Fix long file paths issue in EtwProfiler #2807 #2808
Fix log duplications in TestAdapter #2790
Fix x86 disassembler error for net462 #2792
Fix IsNetCore and IsNativeAOT for single-file apps without AOT #2799
Fix density plot generation in RPlotExporter for latest version of R #2809

`v0.15.2`: 0.15.2

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.2.html

Highlights

The most significant update in this release is the enhanced accuracy of the memory diagnoser (#2562). This improvement resolves the issue of incorrectly reported memory allocations (#1542, #2582).
We have introduced a new feature that allows users to sort benchmark jobs in numerical order (#2768, #2770).
Benchmark validation has been improved (#2771).
An issue with non-persistent auto-generated JobId has been fixed (#2777).

`v0.15.1`: 0.15.1

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.1.html

Highlights

Added support for *.slnx (#2763, #2764)
Enabled ArgumentsSource to reference methods in other types (#2744, #2748)
Resolved fatal errors for ARM CPUs (#2745, #2756)
Fixed bugs related to support for Android, browser, iOS, and tvOS (#2739, #2741, #2740, #2742)

`v0.15.0`: 0.15.0

Full changelog: https://benchmarkdotnet.org/changelog/v0.15.0.html

Giorgi/DuckDB.NET (DuckDB.NET.Data.Full)

`v1.4.3`

Compare Source

`v1.4.1`

Compare Source

`v1.3.2`

Compare Source

`v1.3.0`

Compare Source

`v1.2.1`

Compare Source

`v1.2.0`

Compare Source

dotnet/ef6 (EntityFramework)

`v6.5.1`: EF 6.5.1

What's Changed

Fix for broken NuGet package by @ErikEJ in #2263

Full Changelog: dotnet/ef6@v6.5.0...v6.5.1

`v6.5.0`: EF 6.5.0

What's Changed

New SQL Server / Azure SQL Database provider (contributed by the community) - Microsoft.EntityFramework.SqlServer. This new provider uses the modern SQL Server client Microsoft.Data.SqlClient. For more information about configuration of this provider, see Microsoft.EntityFramework.SqlServer Guide.
The ef6 utility was updated to only support .NET 6 and newer. It was also updated to support reading from app.config files, and support Windows ARM64.
The System.Data.SqlClient driver was updated to version 4.8.6.

Full Changelog: https://github.com/dotnet/ef6/compare/v6.4.4..v6.5.0

`v6.4.4`: EF 6.4.4

This release contains no functional changes. Only the NuGet package icon was updated.

`v6.4.0`: EF 6.4

The primary goal of EF 6.4 is to polish the features and scenarios we delivered in EF 6.3. To this end we have fixed important issues found in EF 6.3 to create a more stable release.

`v6.2.0`

Compare Source

dotnet/sqlclient (Microsoft.Data.SqlClient)

`v6.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.
(#3830)
Updated dependencies (#3843):
- .NET Framework 4.6.2:
  - Azure.Core 1.47.1 -> 1.50.0
  - Azure.Identity 1.14.2 -> 1.17.1
  - Microsoft.Identity.Client 4.80.0 - Added
  - System.Buffers 4.5.1 -> 4.6.1
  - System.Diagnostics.DiagnosticSource 8.0.1 - Added
  - System.IdentityModel.Tokens.Jwt 7.7.1 - Added
  - System.Memory 4.6.3 - Added
  - System.Text.Json 8.0.5 -> 8.0.6
  - System.Text.RegularExpressions 4.3.1 - Added
  - Microsoft.Bcl.Cryptography - Removed
  - System.Text.Encodings.Web - Removed
- .NET 8.0:
  - Azure.Core 1.47.1 -> 1.50.0
  - Azure.Identity 1.14.2 -> 1.17.1
  - Microsoft.Identity.Client 4.80.0 - Added
  - System.Diagnostics.DiagnosticSource 8.0.1 - Added
  - System.IdentityModel.Tokens.Jwt 7.7.1 - Added
  - Microsoft.Bcl.Cryptography - Removed
  - System.Text.Json - Removed
- .NET 9.0:
  - Azure.Core 1.47.1 -> 1.50.0
  - Azure.Identity 1.14.2 -> 1.17.1
  - Microsoft.Extensions.Caching.Memory 9.0.4 -> 9.0.11
  - Microsoft.Identity.Client 4.80.0 - Added
  - System.Configuration.ConfigurationManager 9.0.4 -> 9.0.11
  - System.Diagnostics.DiagnosticSource 9.0.11 - Added
  - System.IdentityModel.Tokens.Jwt 7.7.1 - Added
  - System.Security.Cryptography.Pkcs 9.0.4 -> 9.0.11
  - Microsoft.Bcl.Cryptography - Removed
  - System.Text.Json - Removed
- .NET Standard 2.0:
  - Azure.Core 1.47.1 -> 1.50.0
  - Azure.Identity 1.14.2 -> 1.17.1
  - Microsoft.Extensions.Caching.Memory 9.0.4 -> 8.0.1
  - Microsoft.Identity.Client 4.80.0 - Added
  - System.Configuration.ConfigurationManager 9.0.4 -> 8.0.1
  - System.Diagnostics.DiagnosticSource 8.0.1 - Added
  - System.IdentityModel.Tokens.Jwt 7.7.1 - Added
  - System.Security.Cryptography.Pkcs 9.0.4 -> 8.0.1
  - System.Text.Json 9.0.5 -> 8.0.6
  - Microsoft.Bcl.Cryptography - Removed

`v6.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)

`v6.1.2`

This update includes the following changes since the 6.1.1 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

dotnet/dotnet (Microsoft.EntityFrameworkCore.SqlServer)

`v8.0.18`: .NET 8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.