An open index of dependabot pull requests across open source projects.

Bump the nuget group with 16 updates

Open
Number: #230
Type: Pull Request
State: Open
Author: dependabot[bot] dependabot[bot]
Association: Unknown
Comments: 2
Created: October 03, 2026 at 08:12 AM UTC
(11 days ago)
Updated: October 03, 2026 at 08:15 AM UTC
(11 days ago)
Labels:
dependencies .NET
Description:

Updated Microsoft.AspNetCore.DataProtection.EntityFrameworkCore from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.AspNetCore.DataProtection.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.Identity.EntityFrameworkCore from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.AspNetCore.Identity.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.JsonPatch.SystemTextJson from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.AspNetCore.JsonPatch.SystemTextJson's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.AspNetCore.OpenApi from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Design from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Design's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Sqlite from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Sqlite's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.ApiDescription.Server from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.Extensions.ApiDescription.Server's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore from 10.0.11 to 10.0.12.

Release notes

Sourced from Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Hosting.Abstractions from 10.0.11 to 10.0.12.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Console from 10.0.11 to 10.0.12.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Options.ConfigurationExtensions from 10.0.11 to 10.0.12.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Quartz.Extensions.Hosting from 3.20.1 to 3.22.3.

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

3.22.3

One fix for the 3.x line, additive: no public API change and no schema change. It is a port of a fix found while building Quartz.NET 4.3.

Fixed

  • A database error on one trigger of a fire batch no longer commits half of it. JobStoreSupport.TriggersFired recorded a non-transient error while firing one trigger as that trigger's failure, and committed the batch anyway. On SQL Server and MySQL the commit kept the failed trigger's partial writes, which could leave its [DisallowConcurrentExecution] job's other triggers BLOCKED for good. On PostgreSQL the error aborted the transaction, so the commit silently rolled back triggers already reported fired: their jobs ran while the store still held them as reserved, and could run again after recovery. The failing attempt now rolls back whole, and the batch fires again without that trigger, which is reported failed. Nothing changes when nothing fails. (#​3931, #​3944)

The same fix ships for 4.2 in 4.2.4.

Full Changelog: https://github.com/quartznet/quartznet/compare/v3.22.2...v3.22.3

3.22.2

One fix for the 3.x line, additive: no public API change and no schema change. It is a port of a fix found while building Quartz.NET 4.3.

Fixed

  • A clustered node no longer idles behind a [DisallowConcurrentExecution] job running on another node. When two nodes reserved triggers of the same such job, the node that lost released its trigger back to WAITING, though the job was still running. With one trigger acquired at a time, which is 3.x's default, that trigger then sat at the head of the node's queue. It was skipped on every pass, it hid the triggers due behind it, and the node slept its whole IdleWaitTime (30 s by default). JobStoreSupport now keeps a released trigger BLOCKED while its job runs, and acquisition reads past a trigger it has to skip. Nothing was lost or doubled. (#​3926, #​3936)

The same fix ships for 4.2 in 4.2.3.

Full Changelog: https://github.com/quartznet/quartznet/compare/v3.22.1...v3.22.2

3.22.1

Four fixes for the 3.x line, all additive: no public API change and no schema change. They are ports of fixes found while building Quartz.NET 4.3, plus one found while proving them.

Fixed

  • A trigger no longer fires after Standby() has returned. The scheduler's loop checked whether it was paused before draining its wake-up signal, so a Standby() that landed between the two, most likely while the loop was waiting for a free worker on a busy scheduler, was lost. The round then went on to fire a trigger due within the next IdleWaitTime (30 s by default). (#​3908)
  • A trigger scheduled just after another is no longer passed over, and one held in standby is let go. When two schedule calls landed before the loop read the first, the later one's time overwrote the earlier, more urgent one. That trigger then ran up to IdleWaitTime late, or went through misfire handling. The same overwrite meant Standby() followed by ScheduleJob() could fire a trigger the loop was holding. (#​3908)
  • A row-lock semaphore no longer acts on a transaction SQL Server has ended. When SQL Server aborted a transaction contending for the lock row, the semaphore retried its lock statement inside the dead transaction: error 41302 with memory-optimized locks, or a 1205 deadlock victim. SqlClient ran the retry outside any transaction, so the store acted without holding TRIGGER_ACCESS. UpdateLockRowSemaphore, UpdateLockRowSemaphoreMOT and StdRowLockSemaphore now give up, and JobStoreSupport retries the operation in a fresh transaction. (#​3908)
  • DirectSchedulerFactory.CreateScheduler returns a scheduler whose job store has finished initializing. It started the store's Initialize without waiting for it. A call made before Start() could then run while the store was still probing its optional columns, and fail reading a trigger (IndexOutOfRangeException: MISFIRE_ORIG_FIRE_TIME). A store that fails to initialize now fails CreateScheduler instead of leaving a broken scheduler registered. (#​3908)

Full Changelog: https://github.com/quartznet/quartznet/compare/v3.22.0...v3.22.1

3.22.0

Quartz.NET 3.22.0 carries three fixes to the persistent store's recovery and clustering paths, each found on the 4.0 line and ported here. One of them adds a setting the store never had — a timeout on the statements it issues — which is the public-surface addition that makes this a minor rather than a patch. The schema is 3.20's. Two of the changes alter behaviour, each marked Behavior change worth noting below.

dotnet add package Quartz --version 3.22.0

What changed

  • A job that requested recovery is recovered after a hard kill when the application declares its jobs and triggers through AddJob/AddTrigger and the store already holds them. The declared trigger was applied as a reschedule, which went through ReplaceTrigger and deleted every fired-trigger row of the key — before Start(), so by the time the first cluster check-in or the non-clustered sweep looked for the interrupted execution, its row was gone. A replacement is not a removal: ReplaceTrigger now deletes the trigger row only, and unscheduling still takes the fired rows with it. The replacement of a trigger whose job disallows concurrent execution is stored BLOCKED behind an execution still in flight, as any trigger of that job is, where it used to be stored WAITING and could fire alongside. A fast restart under a stable instance id had a second defect: on its first check-in a node handed its own state row to recovery, and the deferral grace period judged that row by its old timestamp, so the EXECUTING row of a serial job was preserved for a second detection that never came — the node's own record is never deferred now. (#​3759, port of e60bd26eeb)
    • Behavior change worth noting: replacing a trigger keeps its fired-trigger rows, and the replacement of a non-concurrent job's trigger is stored BLOCKED while an execution is in flight.
  • quartz.jobStore.commandTimeout bounds every statement the store issues, the lock statement included. A row lock belongs to the database session that took it, so a node that loses its network without the server noticing keeps TRIGGER_ACCESS locked, and every other node's next lock statement queues behind that dead session — and nothing on this branch bounded the wait: the statement never failed, so the lock handler's retries, DbRetryInterval back-off and the SchedulerError notification never ran, and the cluster stopped firing without logging anything (#​3763). The setting is a millisecond count like every other duration on the store; 0 means the provider's own default (30 seconds for most), a negative value is refused where it is configured, and a value past what ADO.NET can hold in whole seconds is refused for the same reason. It is rounded up to whole seconds, because rounding down would turn a sub-second value into "wait forever". It reaches the driver delegate through DelegateInitializationArgs and the lock handler through DBSemaphore.CommandTimeout, which the store writes once its handler is known — so a handler named by quartz.jobStore.lockHandler.type is bounded too. An unconfigured store imposes nothing. SchedulerBuilder's persistent-store options set it fluently. The troubleshooting page gains the dead-session case: how to tell it apart in each database, why killing a process does not reproduce it, and the server-side settings that are the only thing that frees the lock. 4.x has the same setting as JobStore:CommandTimeout. (#​3764, #​3765)
  • A failed check-in is retried inside the window its peers give it. A peer writes a node off once interval + threshold has passed since the row it last wrote — 15 s on the defaults — and the cluster manager's sleep after a failed check-in was floored at DbRetryInterval, also 15 s, so a check-in that failed at 7.5 s was next attempted after the peers had already recovered the node: its fired-trigger rows deleted, its recovering jobs fired again, [DisallowConcurrentExecution] no longer holding. Java Quartz sleeps the same way, so this is inherited rather than a regression. While the window is still open a failed check-in is now retried inside it — half of what is left each time, never later than DbRetryInterval, never sooner than the loop's pause — and only once it has closed does the ordinary back-off apply. The manager times the window from its own record of the last check-in that reached the database, not from the store's LastCheckin, which a failed read also stamps. Defaults and the 15-second failover latency are unchanged, and threshold >= DbRetryInterval is no longer a relation an operator has to know about. The configuration reference's clusterCheckinInterval default (7500, not 15000) and the missing clusterCheckinMisfireThreshold row were fixed on the way. (port of a5b2197e5d)
    • Behavior change worth noting: after a failed check-in the next attempt comes sooner than DbRetryInterval while the peers' window is still open.

Public API — additive only

  • JobStoreSupport.CommandTimeout, DBSemaphore.CommandTimeout, AdoUtil.CommandTimeout, DelegateInitializationArgs.CommandTimeout, SchedulerBuilder.PersistentStoreOptions.CommandTimeout — the one setting, wherever a statement is prepared.

Upgrading

dotnet add package Quartz --version 3.22.0. Nothing to migrate; the schema is unchanged. The 4.x line is the current major and carries all three fixes as well; the 4.x migration guide is the way there.

Full changelog: https://github.com/quartznet/quartznet/compare/v3.21.0...v3.22.0

3.21.0

Quartz.NET 3.21.0 carries the three fixes held back from 3.20.1 because each needed a small addition to the public surface or changed what a running scheduler does. All three were found while 4.0 was being finished; each is as old as 3.x. The public API grows by two interfaces on one class and nothing else; the schema is 3.20's. Three of the changes alter behaviour, each marked Behavior change worth noting below.

dotnet add package Quartz --version 3.21.0

What changed

  • ResumeAll clears every paused trigger group, not only the ones with triggers — the persistent store resumed the groups it found in QRTZ_TRIGGERS and then deleted only its all-groups marker, so a group paused while it held no triggers kept its QRTZ_PAUSED_TRIGGER_GRPS row and went on pausing whatever was scheduled into it afterwards. Pausing a group before anything is scheduled into it is a documented use of the exact-name matcher, so this was a row the store wrote on purpose and could not take back. The trailing delete now takes every group, as RAMJobStore has always done. (#​3721, #​3742, port of f76b04a468)
    • Behavior change worth noting: a group paused while empty no longer survives ResumeAll.
  • A job store closes its lock handler when it shuts down — RedisSemaphore opened a ConnectionMultiplexer on the first lock and kept it, with its heartbeat, for the life of the process, because nothing on the store's shutdown path reached the lock handler and ISemaphore had no member that meant "we are done". On a branch that targets netstandard2.0 and net462 an interface cannot gain a default member, so JobStoreSupport.Shutdown now disposes a lock handler that implements IAsyncDisposable or IDisposable, after the misfire handler, the cluster manager and the connection manager have stopped, logging and continuing if that throws; RedisSemaphore implements both and closes the multiplexer it opened. (#​3721, #​3742, port of #​3639)
    • Behavior change worth noting: a custom ISemaphore that implements either interface is now disposed at shutdown.
  • A configured wait longer than the platform's timer ceiling is refused where it is set — Task.Delay refuses anything longer than about 49.7 days on .NET and about 24.9 days on .NET Framework, with an ArgumentOutOfRangeException naming a parameter called delay, and every duration Quartz waits out that way was accepted unchecked and reported later from wherever the wait happened. MisfireHandlerFrequency, MisfireThreshold (when it is also the handler's sleep), ClusterCheckinInterval, DbRetryInterval, TransientRetryInterval, the row-lock handlers' RetryPeriod, StartDelayed's argument and QuartzHostedServiceOptions.StartDelay now name the setting, the ceiling and the value at configuration time. The ceiling is per target framework, held to what Task.Delay actually accepts by a test. (#​3721, #​3742, port of #​3577)
    • Behavior change worth noting: a value past the ceiling now fails at configuration rather than later.

Public API — additive only

  • Quartz.Extensions.Redis: RedisSemaphore implements IAsyncDisposable and IDisposable.

Upgrading

dotnet add package Quartz --version 3.21.0. Nothing to migrate. The 4.0 line is the current major; the 4.x migration guide is the way there, and 4.0.1 made the upgrade one a dependency bot can offer.

Full changelog: https://github.com/quartznet/quartznet/compare/v3.20.1...v3.21.0

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.17.2 to 2.17.13.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated TUnit from 1.66.8 to 1.72.16.

Release notes

Sourced from TUnit's releases.

1.72.16

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.10...v1.72.16

1.72.10

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.4...v1.72.10

1.72.4

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.0...v1.72.4

1.72.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.71.0...v1.72.0

1.71.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.70.1...v1.71.0

1.70.1

What's Changed

Other Changes

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.70.0...v1.70.1

1.70.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.24...v1.70.0

1.69.24

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.21...v1.69.24

1.69.21

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.16...v1.69.21

1.69.16

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.0...v1.69.16

1.69.0

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.17...v1.69.0

1.68.17

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.4...v1.68.17

1.68.4

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.0...v1.68.4

1.68.0

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.67.0...v1.68.0

1.67.0

What's Changed

Other Changes

Dependencies

New Contributors

1.66.27

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.66.16...v1.66.27

1.66.16

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.66.10...v1.66.16

1.66.10

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.66.8...v1.66.10

Commits viewable in compare view.

Updated TUnit.AspNetCore from 1.66.8 to 1.72.16.

Release notes

Sourced from TUnit.AspNetCore's releases.

1.72.16

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.10...v1.72.16

1.72.10

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.4...v1.72.10

1.72.4

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.72.0...v1.72.4

1.72.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.71.0...v1.72.0

1.71.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.70.1...v1.71.0

1.70.1

What's Changed

Other Changes

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.70.0...v1.70.1

1.70.0

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.24...v1.70.0

1.69.24

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.21...v1.69.24

1.69.21

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.16...v1.69.21

1.69.16

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.69.0...v1.69.16

1.69.0

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.17...v1.69.0

1.68.17

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.4...v1.68.17

1.68.4

What's Changed

Other Changes

Dependencies

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.68.0...v1.68.4

1.68.0

What's Changed

Other Changes

Dependencies

New Contributors

Full Changelog: https://github.com/thomhurst/TUnit/compare/v1.67.0...v1.68.0

1.67.0

What's Changed

Other Changes

Dependencies

  • chore(de...

Description has been truncated

Technical Details
ID: 16659165
UUID: 5687840522
Node ID: PR_kwDOSdkao88AAAABGaNcvQ
Host: GitHub
Repository: balance-budget/balance-budget