Bump the nuget-minor-patch group with 6 updates by dependabot[bot] · Pull Request #60 · klomkling/themia

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 MySqlConnector from 2.4.0 to 2.6.0.

Release notes

Sourced from MySqlConnector's releases.

2.6.0

Add opt-in stable OpenTelemetry semantic conventions: #1435.
- In MySqlConnector 3.0, the experimental conventions will be removed.
- Applications should set OTEL_SEMCONV_STABILITY_OPT_IN to database or database/dup (or use WithSemanticConventionsKinds) to test the new semantic conventions.
Support distributed tracing by sending traceparent to MySQL Server: #1635.
EnableResultSetHeaderEvent is now opt-in: #1633.
Move AddMySqlDataSource and related APIs from MySqlConnector.DependencyInjection to MySqlConnector: #1649.
Improve reliability and correctness of parameter parsing and rewriting:
- Fix termination of quoted parameters: #1627.
- Handle all comment-start characters during SQL parsing: #1624.
- Add stricter argument validation and checks: #1632.
Improve XA and transaction handling:
- Handle more XA error codes: #1631.
- Clear transaction when closing a database: #1623.
- Handle missing transaction in DoCloseAsync: #729.
Improve data type handling:
- Reject negative DATETIME ticks: #1630.
- Don't detect BINARY columns as Guid: #1625.
Improve exception safety: #1628.
Suppress trimming warnings and update AOT test coverage: #1607, #1608.
Thanks to @markus456 and @sbomer for contributions to this release.

2.5.0

Support .NET 10: #1595.
Possibly breaking MySqlConnection.State will be set to ConnectionState.Broken when there is a network error: #1599.
- Previously it would have been set to ConnectionState.Closed but the connection wasn't truly closed.
- Call MySqlConnection.Close() to fully close the connection before calling Open() again.
- Better yet, call .Dispose() (ideally with a using declaration) and create a new MySqlConnection instance to recover from failure.
Possibly breaking MySqlConnection.ResetConnectionAsync will consistently throw a MySqlException: #1602.
Implement MariaDB PARSEC authentication: #1540, #1606.
Support the VECTOR data type: #1549.
Implement COM_STMT_SEND_LONG_DATA to stream large parameter values: #943.
Add MySqlConnectorTracingOptions and builder APIs to configure tracing output: #1524.
Read Guid values from stored procedure out parameters: #1528.
Mark MySqlDbType with [DbProviderSpecificTypeProperty(true)]: #1557.
Allow loopback connections (e.g., Google Cloud SQL Proxy) to use clear-text password or public key retrieval: #1534, #1542.
Improve schema metadata with MariaDB by reading stored procedure metadata from mysql.proc: #1547.
Improve XA transaction rollback handling: #1585, #1589.
Free large cached payload buffers when returning sessions to the pool to reduce memory usage: #1587.
Suppress error-level logging when a command is canceled: #1544.
Fix MySqlBulkCopy auto-detected column mappings: #1568.
Fix Foreign Keys schema SQL syntax: #1601.
Fix extra roundtrip for caching_sha2_password: #1562.
Fix cancellation with AWS RDS Proxy: #1581.
Optimization: Use System.Threading.Lock for .NET 9.0+.
Optimization: Use PemEncoding in .NET 5.0+ and UTF-8 methods in .NET 10.0+.
Thanks to @djeman, @jnoordsij, @NETSphereSoft, @PatrickMNL, @petedishman, and @rusher for contributions to this release.

2.5.0-beta.1

2.5.0 Beta 1

Support .NET 10: #1595.
Possibly breaking MySqlConnection.State will be set to ConnectionState.Broken when there is a network error: #1599.
- Previously it would have been set to ConnectionState.Closed but the connection wasn't truly closed.
- Call MySqlConnection.Close() to fully close the connection before calling Open() again.
- Better yet, call .Dispose() (ideally with a using declaration) and create a new MySqlConnection instance to recover from failure.
Possibly breaking MySqlConnection.ResetConnectionAsync will consistently throw a MySqlException: #1602.
Implement MariaDB PARSEC authentication: #1540.
Support the VECTOR data type: #1549.
Implement COM_STMT_SEND_LONG_DATA to stream large parameter values: #943.
Add MySqlConnectorTracingOptions and builder APIs to configure tracing output: #1524.
Read Guid values from stored procedure out parameters: #1528.
Mark MySqlDbType with [DbProviderSpecificTypeProperty(true)]: #1557.
Allow loopback connections (e.g., Google Cloud SQL Proxy) to use clear-text password or public key retrieval: #1534, #1542.
Improve schema metadata with MariaDB by reading stored procedure metadata from mysql.proc: #1547.
Improve XA transaction rollback handling: #1585, #1589.
Free large cached payload buffers when returning sessions to the pool to reduce memory usage: #1587.
Suppress error-level logging when a command is canceled: #1544.
Fix MySqlBulkCopy auto-detected column mappings: #1568.
Fix Foreign Keys schema SQL syntax: #1601.
Fix extra roundtrip for caching_sha2_password: #1562.
Fix cancellation with AWS RDS Proxy: #1581.
Optimization: Use System.Threading.Lock for .NET 9.0+.
Optimization: Use PemEncoding in .NET 5.0+ and UTF-8 methods in .NET 10.0+.
Thanks to @djeman, @jnoordsij, @NETSphereSoft, @PatrickMNL, @petedishman, and @rusher for contributions to this release.

Commits viewable in compare view.

Updated Npgsql from 10.0.2 to 10.0.3.

Release notes

Sourced from Npgsql's releases.

10.0.3

Release milestone

Full Changelog: npgsql/npgsql@v10.0.2...v10.0.3

Commits viewable in compare view.

Updated Quartz from 3.18.0 to 3.18.1.

Release notes

Sourced from Quartz's releases.

3.18.1

Quartz.NET 3.18.1 is a maintenance release that addresses a timezone-related bug, security advisories on transitive dependencies, and an issue that prevented the new Redis distributed-lock package from publishing to nuget.org.

Highlights

Fix GetTimeBefore for positive-offset timezones — CronExpression.GetTimeBefore could throw ArgumentOutOfRangeException for cron expressions evaluated against timezones with positive UTC offsets (e.g. Europe/Helsinki, Asia/Tokyo). Backported from main.
Redis package renamed to Quartz.Extensions.Redis — the original Quartz.Redis package id from 3.18.0 collided with an unrelated v1.0.0 already on nuget.org and could not be published. The 3.18.0 release was shipped with IsPackable=false as a workaround; 3.18.1 picks the umbrella id Quartz.Extensions.Redis (matching Quartz.Extensions.DependencyInjection / Quartz.Extensions.Hosting) and re-enables publication. There are no consumers to migrate — the original id was never on nuget.org.
Vulnerable transitive dependency bumps — addresses moderate advisories that were blocking restore on the 3.x CI pipeline.

What's Changed

Fix GetTimeBefore throwing for positive-offset timezones (#3046) by @lahma in Fix GetTimeBefore throwing for positive-offset timezones (#3046) quartznet/quartznet#3047
Bump vulnerable packages to unblock 3.x CI by @lahma in Bump vulnerable packages to unblock 3.x CI quartznet/quartznet#3054
Rename Quartz.Redis package to Quartz.Extensions.Redis by @lahma in Rename Quartz.Redis package to Quartz.Extensions.Redis quartznet/quartznet#3053

Full Changelog: quartznet/quartznet@v3.18.0...v3.18.1

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

Bumps Dapper from 2.1.66 to 2.1.79 Bumps FluentValidation from 11.11.0 to 11.12.0 Bumps Microsoft.Data.SqlClient from 6.0.1 to 6.1.5 Bumps MySqlConnector from 2.4.0 to 2.6.0 Bumps Npgsql from 10.0.2 to 10.0.3 Bumps Quartz from 3.18.0 to 3.18.1 --- updated-dependencies: - dependency-name: Dapper dependency-version: 2.1.79 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: FluentValidation dependency-version: 11.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Microsoft.Data.SqlClient dependency-version: 6.1.5 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: MySqlConnector dependency-version: 2.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-patch - dependency-name: Npgsql dependency-version: 10.0.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch - dependency-name: Quartz dependency-version: 3.18.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-patch ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot Bot added the dependencies Dependency updates label Jun 8, 2026

github-actions Bot enabled auto-merge (squash) June 8, 2026 23:14

github-actions Bot merged commit c6739cf into main Jun 8, 2026
3 checks passed

dependabot Bot deleted the dependabot/nuget/nuget-minor-patch-0efe306bd3 branch June 8, 2026 23:15

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Bump the nuget-minor-patch group with 6 updates#60

Bump the nuget-minor-patch group with 6 updates#60
github-actions[bot] merged 1 commit into
mainfrom
dependabot/nuget/nuget-minor-patch-0efe306bd3

dependabot Bot commented on behalf of github Jun 8, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Jun 8, 2026

2.1.79

What's Changed

New Contributors

2.1.72

What's Changed

New Contributors

6.1.5

Fixed

Target Platform Support

Dependencies

.NET Framework 4.6.2

.NET 8.0

.NET 9.0

6.1.4

Fixed

Added

AppContext Switch for enabling MultiSubnetFailover

Changed

6.1.3

Added

App Context Switch for Ignoring Server-Provided Failover Partner

Fixed

Target Platform Support

Dependencies

.NET Framework 4.6.2+

6.1.2

Fixed

6.1.1

Fixed

Changed

6.1.0

Release Notes

Stable Release 6.1.0 - 2025-07-25

Added

Added dedicated SQL Server vector datatype support

Revived .NET Standard 2.0 target support

6.1.0-preview2

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

Added

Added dedicated SQL Server vector datatype support

Revived .NET Standard 2.0 target support

6.1.0-preview1

Added

Fixed

Changed

New Contributors

6.0.5

[Stable release 6.0.5] - 2026-01-15

Fixed

Added

Changed

6.0.4

Added

App Context Switch for Ignoring Server-Provided Failover Partner

Target Platform Support

Dependencies

.NET Framework

.NET 8

6.0.3

Fixed

Changed

6.0.2

Fixed

Changed

2.6.0

2.5.0

2.5.0

2.5.0-beta.1

2.5.0 Beta 1

10.0.3

3.18.1

Highlights

What's Changed

Uh oh!

Uh oh!

Reviewers

Assignees

Labels