Skip to content

Bump the nuget group with 6 updates - #435

Merged
karirafn merged 2 commits into
mainfrom
dependabot/nuget/main/nuget-e4b668284e
Nov 4, 2026
Merged

karirafn merged 2 commits into
mainfrom
dependabot/nuget/main/nuget-e4b668284e

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 4, 2026

Copy link
Copy Markdown
Contributor

Updated Microsoft.AspNetCore.OpenApi from 10.0.13 to 10.0.14.

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.13 to 10.0.14.

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.InMemory from 10.0.13 to 10.0.14.

Release notes

Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Sqlite from 10.0.13 to 10.0.14.

Release notes

Sourced from Microsoft.EntityFrameworkCore.Sqlite's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Quartz.Extensions.Hosting from 4.5.0 to 4.7.2.

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

4.7.2

Fixes for the 4.7 line, most of them for .NET 11. There is no public API change and no schema change.

Fixed

  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK.
    • The symptom: a host built in Debug with the .NET 11 SDK never made a dashboard at a custom DashboardPath interactive, because the Blazor circuit never started.
    • The cause: the SDK adds a hot-reload JS initializer (_framework/Microsoft.NET.Sdk.BlazorWeb.DotNetWatch.<hash>.lib.module.js) to every Debug build of a Blazor host, even without dotnet watch. The dashboard's <base href> sends that request under the dashboard path, but the dashboard mirrored only blazor.web.js and opaque-redirect there. So the request failed, and the failed import stopped Blazor.start.
    • The fix: the dashboard now serves the whole _framework tree under its path, forwarding each file to what the host serves at /_framework/.
    • Not affected: the default /quartz path, Release and publish builds, and builds with the .NET 10 SDK.
    • Thanks to the Marten Studio maintainers, who found it in their port of the dashboard's mount code. (#​4225, closes #​4224)
  • On .NET 11, agents register with a dashboard that uses a fail-closed FallbackPolicy.
    • The symptom: on ASP.NET Core 11, a dashboard host with the fail-closed FallbackPolicy the dashboard recommends turned away every agent, even one with the right token.
    • The cause: ASP.NET Core 11 holds a hub method that carries any attribute to the FallbackPolicy, whatever the hub's endpoint allows (dotnet/aspnetcore#​69624). The compiler puts AsyncStateMachineAttribute on every async method, so the agent hub's Register was held to the policy, and so were the live-events hub's methods.
    • The fix: the dashboard's hub methods are no longer async, so they carry no attribute. The agent hub's own token check is unchanged.
    • Still affected: a dashboard mapped with AllowAnonymous() under a fail-closed FallbackPolicy doesn't start its Blazor circuit on .NET 11 for an unauthenticated user. Blazor's own StartCircuit meets the same ASP.NET Core issue, which only ASP.NET Core can fix. (#​4235, closes #​4234)
  • A delegate job beside AddDeclaredJobs() is intercepted in a net11.0 build.
    • The symptom: in an app targeting net11.0, a ScheduleJob or AddJob delegate in the same AddQuartz lambda as AddDeclaredJobs() got no generated interceptor. It fell back to reflection binding, which a trimmed or native AOT app can't use.
    • The cause: the delegate-jobs generator can't see the registration the declared-jobs generator writes. Against the .NET 11 reference assemblies, the compiler resolved the unbound lambda to another AddQuartz overload.
    • The fix: the generator now binds such a call again, against a stand-in for that registration. A delegate call chained onto AddDeclaredJobs() is now intercepted too, which it never was before on any target framework. (#​4235, closes #​4234)
  • On .NET 11, a 500 from the scheduler HTTP API keeps its problem-details title. ASP.NET Core 11 retitled 500 (dotnet/aspnetcore#​65590), so the HTTP API's 500 body changed with the runtime. The HTTP API now writes every problem's type and title from its own table, which is ASP.NET Core 10's, so the body is the same on every runtime. The agent's 413 and 501 bodies gain the type and title the HTTP API already wrote. (#​4235, closes #​4234)
  • Stopping a host twice at once no longer throws from the dashboard's attached-store discovery. A host started with Run or RunAsync stops itself once its stopping token fires. A second stop from elsewhere, such as an application's own StopAsync or a test host's dispose, then ran AttachedStoreDiscovery.StopAsync at the same time. That threw InvalidOperationException: Collection was modified, even with no store attached. (#​4230, closes #​4229)

The 3.x line gets the dashboard _framework fix in 3.22.10. None of the others apply to 3.x, which has no attached-store discovery, no agent hub, no HTTP API problem details and no source generators.

What's Changed

Full Changelog: quartznet/quartznet@v4.7.1...v4.7.2

4.7.1

Two fixes for the 4.7 line: decimals read back correctly on .NET 11, and NativeJob works properly on Linux. There is no public API change and no schema change.

Fixed

  • On .NET 11, a job-data number read as a decimal comes back as the number that was written. .NET 11 converts a double or float to the decimal nearest its exact binary value, so JobDataMap.Get<decimal> of 12.34d returned 12.339999999999999857891452848. Nothing threw, so a job reading an amount silently got a different number after the runtime upgrade. The values affected are a double or float in job data: untyped JSON numbers, scheduling data, the HTTP API, or Put("amount", 12.34). So are the DEC_PROP_1/2 trigger columns, when a driver such as SQLite's returns NUMERIC as a double. Quartz now rounds those to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4216, closes #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string, which .NET splits on whitespace, so /bin/sh -c echo hi ran echo alone and the parameters never reached the command. (#​4215, closes #​4212)
  • Cancelling a waiting NativeJob kills the process tree. An interrupt or a shutdown left the child running, and the job reported the cancellation as Error launching native command. The job now kills the process and its descendants, and ends as cancelled (OperationCanceledException) rather than failed. (#​4215)
  • NativeJob reads output without foreground threads. Two foreground threads read stdout and stderr, so a child that held its pipes open kept the host process alive after shutdown. Asynchronous reads replace them. When the job waits, all output is logged before it completes, unless a process the command started keeps the streams open more than 5 seconds after it exits; event 7204 then says so. (#​4215)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4215)

Compatibility

  • On Linux, a NativeJob command that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments to Parameters.
  • A cancelled NativeJob now ends as cancelled rather than with a JobExecutionException. Listeners and history see a cancellation.

The 3.x line gets the same fixes in 3.22.10.

What's Changed

Full Changelog: quartznet/quartznet@v4.7.0...v4.7.1

4.7.0

Quartz.NET 4.7 is about running a schedule the way it was meant. Four additions cover that:

  • A simple trigger can measure its interval from the previous run's completion.
  • A scheduler-wide default time zone applies to every trigger that names none.
  • A declared trigger can be switched off from configuration with -.
  • The HTTP API and every dashboard trigger page show a trigger's upcoming fire times.

A stored typed job can be run now with its input. SQL Server joins lock-free firing rounds when READ_COMMITTED_SNAPSHOT is on. An application on 4.6 compiles on 4.7 unchanged. One behaviour change needs checking: CronExpressionBuilder now writes 0 for an unset seconds field. The upgrade has one required database migration, a nullable column that can run while 4.6 nodes are up. See Upgrading from 4.6 to 4.7.

dotnet add package Quartz --version 4.7.0

Highlights

  • Fixed-delay schedules. SimpleScheduleBuilder.MeasureIntervalFromCompletion() starts the next run an interval after the previous one completes, so a long run never queues the next one behind it. Triggers
  • A default time zone. UseDefaultTimeZone (Scheduler:DefaultTimeZone) gives its zone to every cron, calendar-interval, daily time-interval and recurrence trigger that names none. Triggers
  • Upcoming fire times. IScheduler.GetUpcomingFireTimes computes a stored trigger's next fire times. The HTTP API serves them at …/fire-times, and every trigger page on the dashboard shows them. Dashboard and HTTP API
  • - switches a declared trigger off. A ConfigurationKey value, or a Quartz:Schedule expression, interval or rule, of - leaves that trigger unscheduled and removes a stored copy. Configuration
  • A typed manual run. TriggerJob<TInput>(jobKey, input) fires an IJob<TInput> now with its input, and returns the trigger's key. Triggers
  • Lock-free rounds on SQL Server. With READ_COMMITTED_SNAPSHOT on and at least two live 4.7 nodes, a round of concurrent-allowed work takes no lock, and claims and fires in two transactions. Clustering
  • One registration for your own types under trimming. AddJsonTypeInfoResolver hands the scheduler your JsonSerializerContext once, for job data and for job inputs. Trimming and native AOT

Triggers

  • A simple trigger can measure its interval from completion (#​4154, closes #​4140).
    • It is MeasureIntervalFromCompletion on the builder, on [SimpleTrigger], in the JSON and XML schedules, through the HTTP API's update-details and in the dashboard's Edit details.
    • It is stored in the nullable QRTZ_TRIGGERS.FIXED_DELAY, from the required migration 4.7/add_trigger_fixed_delay. A 4.6 node runs such a trigger at a fixed rate, so turn it on only once every node is 4.7.
  • A scheduler-wide default time zone (#​4146, closes #​4135). It is QuartzSchedulerOptions.DefaultTimeZone, or UseDefaultTimeZone(TimeZoneInfo). The keys are Scheduler:DefaultTimeZone and quartz.scheduler.defaultTimeZone, and take an IANA or Windows id. A trigger that names a zone keeps it. InTimeZone(null) now means "no zone stated".
  • TriggerJob<TInput> runs a stored typed job now with its input, and returns the manual trigger's TriggerKey, for history and fire-instance lookups. TriggerJob(jobKey, token) now compiles and fires the job with no data (#​4150, closes #​4138).
  • CronExpressionBuilder leaves an unset seconds field at 0, not * (#​4144, closes #​4143). WithMinuteIncrements(0, 5) used to build * 0/5 * ? * *, every second of every fifth minute. It now builds 0 0/5 * ? * *. To fire every second, add WithSecondRange(0, 59).
  • A start that re-applies a declared trigger keeps its run state (#​4147, closes #​4128). While the schedule is unchanged, it keeps TimesTriggered, a pending retry and an individual pause, so a finite repeat count does not start over. Also in 4.6.1 and 3.22.8.

Clustering

  • Lock-free firing rounds on SQL Server (#​4157, closes #​4117). These need READ_COMMITTED_SNAPSHOT on and at least one other live 4.7 node. A single node keeps 4.5's rounds (reason no_live_peer), because there they measured slower. Without the setting, rounds stay locked (reason read_committed_snapshot_off, which replaces sql_server). See SQL Server.
  • Interrupt follow-ups (#​4153, closes #​4141). A dashboard cluster row asks the preferred member, and the next only if that fails. A store-attached dashboard window can interrupt a firing on a live 4.6+ node. FireInstance.InterruptRequestedUtc shows a pending request.
  • A node with a generated instance id warns about triggers pinned to a fixed node, which can never match it (event 4031; #​4145, closes #​4139).
  • A recovered firing of an ungrouped trigger counts against its trigger group's execution limit under UseTriggerGroupWhenUnset, not against RECOVERING_JOBS (#​4148, closes #​4142). Also in 4.6.1.
  • A serial job's completion reads only the triggers that misfired, not its whole backlog (#​4169, from #​4167). Thanks @​kostekk88 for the report and the harness. Also in 4.6.1.
  • A manual firing reads only the group column of its job's triggers to find their shared execution group (#​4179, closes #​4174). Also in 4.6.3.

Dashboard and HTTP API

  • Upcoming fires on every trigger page (#​4152, closes #​4136). They are read through IQuartzApiClient.GetUpcomingFireTimes, a default interface member, from the route GET …/triggers/{group}/{name}/fire-times. The agent operation is GetTriggerFireTimes. A fixed-delay trigger shows its next run as provisional. The cron editor's preview shows only while the edited expression differs from the saved one (#​4159).
  • An agent's goodbye is heard before it disconnects (#​4201, closes #​4176). Unregister at scheduler shutdown was sent without waiting for delivery, and stopping the connection could drop it, so the dashboard listed the agent as disconnected instead of shut down.

Configuration

  • A configured schedule of - switches a declared trigger off (#​4151, closes #​4137). It applies to a ConfigurationKey value, and to the JSON schedule's Cron.Expression, Simple.Interval and Recurrence.Rule. The trigger is not scheduled, a stored copy is unscheduled, and event 4032 is logged.
    ... (truncated)

4.6.3

Two fixes for the 4.6 line, for applications that are not yet ready for 4.7's database migration. There is no public API change and no schema change.

Fixed

  • Quartz.Weasel.MySQL floors MySqlConnector at 2.6.1. 4.6.2 took the driver from Weasel.MySql 9.39.0, which declares 2.4.0, so its nuspec carried a floor that GHSA-473q-m89c-ghf8 covers: the driver sends the password before it has verified the server's TLS certificate. The package now names MySqlConnector itself, at the first fixed version. An application that already references 2.6.1 or later is unaffected. (#​4204, from #​4197)
  • A manual firing reads only the group column of its job's triggers. To find the execution group a job's triggers share, TriggerJob listed every trigger's header. On the ADO.NET store that meant every column of every trigger, a fired-trigger probe per row and a sort. On RAMJobStore it meant a walk of the whole store. Each firing not yet run made the next listing longer. A shipped delegate now reads EXECUTION_GROUP alone, and stops at the first row that settles the answer. On SQLite with 4,000 triggers, TriggerJob drops from 38.6 ms to 12.4 ms. (#​4204, from #​4179 and #​4174)

Dependency change

  • Quartz.Weasel.MySQL gains a direct dependency on MySqlConnector (>= 2.6.1).

4.7.0 carries both fixes. No 3.x package references MySqlConnector, and 3.x has had the manual-firing fix since 3.22.8.

What's Changed

Full Changelog: quartznet/quartznet@v4.6.2...v4.6.3

4.6.2

One fix for the 4.6 line. There is no public API change, no schema change and no dependency change.

Fixed

  • Legacy time zone names resolve on a system without tzdata-legacy, such as Ubuntu 26.04. Without the TimeZoneConverter plugin, seven Windows ids (FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time) and tzdata's legacy IANA names, such as Asia/Calcutta and Europe/Kiev, threw TimeZoneNotFoundException there. For those seven Windows ids, .NET maps through CLDR to the legacy names, which only tzdata-legacy installs. Quartz now maps a legacy name to its canonical zone through tzdata 2026e's backward links, and resolves it under the id asked for. The id a store writes to TIME_ZONE_ID therefore does not depend on whether the host has tzdata-legacy. (#​4180, from #​4172)

Behaviour change

  • With UseTimeZoneConverter on such a host, 4.6.1 stored the canonical name (TimeZoneConverter 7.1.0 answers Europe/Kyiv for FLE Standard Time). 4.6.2 resolves the id before the plugin is asked, so it stores the id asked for. Rows already stored read back either way.

The same fix ships for 3.x in 3.22.9.

What's Changed

Full Changelog: quartznet/quartznet@v4.6.1...v4.6.2

4.6.1

Fixes from 4.7's development for the 4.6 line. There is no public API change and no schema change. Quartz.Plugins.TimeZoneConverter now requires TimeZoneConverter 7.1.0; no other package's dependencies change.

Fixed

  • A start no longer resets a declared trigger's run state. Creating a scheduler re-applies every AddTrigger and ScheduleJob registration and every scheduling file through RescheduleJob. That reset TimesTriggered, so a finite WithRepeatCount or a recurrence rule's COUNT ran again from the beginning. It also dropped a retry pending at shutdown, and resumed a trigger an operator had paused on its own. While the declared schedule is unchanged, the count and the retry are now kept, and so is the pause, with its record. A changed schedule starts fresh, and an application's own RescheduleJob still ends an individual pause. (#​4147, from #​4128)
  • A [DisallowConcurrentExecution] job's completion reads only the triggers that misfired. Each completion read every waiting trigger of the job in full under TRIGGER_ACCESS to find the late ones, so draining a backlog read N rows on each of N completions, and scheduling calls waited behind the lock. A shipped delegate now reads only the job's misfired triggers, with the misfire handler's own predicate. In the #​4167 workload on SQL Server (400 queued triggers on one serial job, 50 ms body), the drain went from 138 s with 137 misfire events to 101 s with 37. (#​4169, from #​4167)
  • A declared job-data type with a number, a boolean or a nested object reads back. A value of a type declared through AddTypeInfoResolver was stored, and then its job failed to load with Failed to parse JobDataMap from json. It now reads back as a Dictionary<string, string> of its members: a number or a boolean as its JSON text ("3", "true"), a nested object as its JSON, a null as null. A map that 4.6.0 stored loads. (#​4161, from #​4156)
  • A recovered firing of an ungrouped trigger is limited under its trigger group. Under UseTriggerGroupWhenUnset, a firing replayed after cluster recovery, a shutdown hand-back or startup recovery was limited under RECOVERING_JOBS, so it ran beside its group's live firings whatever the group's limit. (#​4148, from #​4142)
  • Startup recovery of a replay keeps the firing it replays. A replay of a replay named the recovery trigger rather than the original firing, and lost the original group's execution limit. Cluster recovery already kept it. (#​4160)
  • A cron trigger's clone has a job data map of its own. CronTriggerImpl.Clone shared the original's map, so a write through either was seen by both. The other trigger types already copied it. (#​4160)
  • Quartz.Plugins.TimeZoneConverter resolves seven more Windows ids on a system without tzdata-legacy, such as Ubuntu 26.04: FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time. Their CLDR names are legacy links that only tzdata-legacy installs, and TimeZoneConverter 7.1.0 maps them to the canonical names. Without the plugin those ids still fail on such a system; #​4172 tracks that. (#​4171)

Behaviour changes

  • A declared collection, or a declared object with a collection member, is refused when the map is written. The JsonSerializationException names the entry, the type and the member. Such a value used to be stored and then fail to load. (#​4161)
  • The ADO store's completion no longer reports a late IgnoreMisfirePolicy trigger as misfired. This applies to the completion of a [DisallowConcurrentExecution], BufferOne or CancelPrevious firing, which also no longer writes such a trigger back. Acquisition fires it late, as the misfire handler and RAMJobStore already did. (#​4169)

The run-state and serial-completion fixes ship for 3.x in 3.22.8.

What's Changed

Full Changelog: quartznet/quartznet@v4.6.0...v4.6.1

4.6.0

Quartz.NET 4.6 is about clusters under load. A firing round of work that allows concurrent execution takes no TRIGGER_ACCESS lock, and a round reads each concern once whatever its size. An interrupt reaches the node running the firing, through the store. A node can serve only the execution groups it is configured for, and execution history can write behind. A trimmed or native publish now records no Quartz trim warning, and eight packages are proven under native AOT. An application on 4.5 compiles on 4.6 unchanged, unless it treats warnings as errors and has a cron literal that the new analyzer warning QZ0007 reports. The upgrade has three required database migrations, each one nullable column that can run while 4.5 nodes are up; see Upgrading from 4.5 to 4.6.

dotnet add package Quartz --version 4.6.0

Highlights

  • Lock-free firing rounds. On a clustered ADO.NET store, a round whose candidates all allow concurrent execution claims its triggers with guarded writes instead of taking TRIGGER_ACCESS. It is on by default, with an off switch. While any 4.5 node is live, every round takes the lock as before. SQL Server keeps the lock. Clustering
  • One read per concern. A clustered firing round reads each concern once, whatever its size, and a one-off's lock-free completion is one read and one write. Clustering
  • Interrupts reach every node. On a clustered store, Interrupt and InterruptFireInstance record a request for a firing on another node, and that node cancels the job's token after its next check-in. CancelPrevious now works across nodes too. Clustering
  • Execution-group routing. A node lists the execution groups it serves, or the ones it refuses, and acquires nothing else. Manual, startup and recovered firings keep their job's group. Execution groups
  • History can write behind. With ExecutionHistoryOptions.WriteBehindInterval set, a completion is queued and flushed with one status update per job per flush, at close to history-off throughput. Execution history
  • A trigger's own misfire threshold, and a scheduler-wide default instruction. WithMisfireThreshold lets one trigger tolerate a longer delay, or a shorter one, without moving the store's threshold for every other trigger. DefaultMisfireHandling sets what an unstated misfire instruction becomes, for every trigger type. Triggers
  • No Quartz trim warnings. The trim baseline is gone, and three feature switches turn the reflective paths off under PublishTrimmed and PublishAot. Quartz.Weasel.SQLite joins the packages proven native on every pull request. Trimming and native AOT

Clustering

  • Lock-free firing rounds (#​4123, closes #​4067).
    • AdoJobStoreOptions.LockFreeFiringRounds, default true; flat key quartz.jobStore.lockFreeFiringRounds. false restores 4.5's rounds.
    • Each node stamps its Quartz version in the new QRTZ_SCHEDULER_STATE.QUARTZ_VERSION, from the required migration 4.6/add_scheduler_version. While any 4.5 node is live, every round takes the lock (event 3517); once the last one ages out, rounds go lock-free (event 3518).
    • SQL Server keeps the lock. A round that needs it, such as one with a [DisallowConcurrentExecution] candidate, takes it.
    • A clustered round that loses a claim runs the following rounds locked (reason contention, event 3060) until the backlog clears or 2 s pass, so a drained backlog is no slower than under 4.5.
    • Measured on PostgreSQL: 3–24% more firings per second than 4.5 in the throughput census.
  • One read per concern (#​4086, closes #​4066).
  • Cluster-wide interrupt (#​4130, closes #​4071).
    • A request is a nullable INTERRUPT_REQUESTED_TIME on the firing's QRTZ_FIRED_TRIGGERS row, from migration 4.6/add_fired_trigger_interrupt. The node running the firing reads its requests after every check-in, so a request lands within one CheckinInterval, 7.5 seconds by default.
    • true from Interrupt means interrupted here or asked, not stopped.
    • A 4.5 node never reads the request; a 4.6 node says so once per such node (event 3520).
    • CancelPrevious asks a 4.6 peer instead of waiting as BufferOne. The two firings overlap for up to one check-in interval.
  • A clustered scheduler generates its instance id unless one was chosen (#​4105, closes #​4091). UseClustering() used to leave every node at NON_CLUSTERED.

Execution groups

  • A node serves the execution groups it is configured for (#​4088, closes #​4069).
  • Manual and startup firings carry their job's execution group (#​4109, closes #​4092).
  • A recovered trigger keeps its job's execution group (#​4084, closes #​4081).
  • Names in IConfiguration keep their case, and an execution-limit prefix such as tenant:* can be configured (#​4107, closes #​4093).

Execution history

  • Write-behind (#​4125, closes #​3979). ExecutionHistoryOptions.WriteBehindInterval queues each completion; one writer per store flushes every interval, or at 256 waiting runs, in one transaction with one QRTZ_JOB_STATUS update per job. In the census, history on ran at 276 firings per second, write-behind at 379, and history off at 388.
    • A crash loses the queue, normally at most one interval of runs. Reads of history and job status lag by up to one interval. Off by default.
  • Lookups by exact trigger key and fire instance id, on two indexes of their own (#​4094, closes #​4072). Optional migration 4.6/add_execution_history_lookup_indexes.

Triggers

  • A trigger carries its own misfire threshold (#​4131, closes #​4070).
    • TriggerBuilder<TJob>.WithMisfireThreshold(TimeSpan), ITrigger.MisfireThreshold: positive, whole milliseconds; null is the store's MisfireThreshold, as before.
    • Every surface carries it: [CronTrigger]/[SimpleTrigger] MisfireThreshold (checked by the new analyzer error QZ0008), the JSON and XML schedules, TriggerDetailsUpdate, the HTTP API's update-details and the dashboard's Edit details.
      ... (truncated)

4.5.1

Three packages take the fixed versions of dependencies named in Microsoft's October 13 security advisories. There is no public API change and no schema change, and no other package changes.

Fixed

  • Quartz.Dashboard.Agent requires Microsoft.AspNetCore.SignalR.Client 10.0.13. 4.5.0 required 10.0.0, and every SignalR client before 10.0.13 brings a Microsoft.AspNetCore.SignalR.Common covered by GHSA-334f-vvp4-7g6p (CVE-2026-70159). So an application referencing the agent got NU1903 at restore, and that is an error wherever warnings are errors. The fixed client asks for Microsoft.Extensions.DependencyInjection, Logging and Logging.Abstractions 10.0.13 or later, so an application referencing the agent now resolves those at least that high. The agent's own nuspec no longer repeats the framework-extension floors it inherits from Quartz. (#​4065)
  • Quartz.Weasel.Oracle and Quartz.Weasel.SqlServer require System.Security.Cryptography.Pkcs 9.0.21. Their database drivers, reached through Weasel, bring Pkcs 8.0.0 and 9.0.4, which GHSA-2fmv-rv2c-59x7 and GHSA-846f-f764-76mx cover. Neither package calls it. The direct reference lifts an application's graph to the fixed version, and can go once the drivers require a fixed one themselves. (#​4065)

The same SignalR fix ships for 3.x's Quartz.Dashboard in 3.22.6.

What's Changed

Other changes

Full Changelog: quartznet/quartznet@v4.5.0...v4.5.1

Commits viewable in compare view.

Updated TMDbLib from 3.0.0 to 4.0.0.

Release notes

Sourced from TMDbLib's releases.

4.0.0

Major changes:

  • Migrated from Newtonsoft.Json to System.Text.Json
  • Native AOT and trimming support: all runtime reflection removed, enum mappings generated at build time by a source generator
  • Reworked the object model to match the current TMDb v3 API / OpenAPI spec (shared TmdbEntity base, duplicate classes removed)
  • Added a catalog of TMDb error codes and handling for them
  • Added async accessors for paginated results
  • Added season-level aggregate credits

Breaking changes:

  • Custom serialization code or converters that rely on Newtonsoft.Json need to be migrated to System.Text.Json
  • Many model classes and properties were renamed, merged or removed to match the TMDb API

What's Changed

New Contributors

Full Changelog: jellyfin/TMDbLib@v3.0.0...v4.0.0

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 Microsoft.AspNetCore.OpenApi from 10.0.13 to 10.0.14
Bumps Microsoft.EntityFrameworkCore.Design from 10.0.13 to 10.0.14
Bumps Microsoft.EntityFrameworkCore.InMemory from 10.0.13 to 10.0.14
Bumps Microsoft.EntityFrameworkCore.Sqlite from 10.0.13 to 10.0.14
Bumps Quartz.Extensions.Hosting from 4.5.0 to 4.7.2
Bumps TMDbLib from 3.0.0 to 4.0.0

---
updated-dependencies:
- dependency-name: Microsoft.AspNetCore.OpenApi
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.Design
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.InMemory
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Microsoft.EntityFrameworkCore.Sqlite
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: Quartz.Extensions.Hosting
  dependency-version: 4.7.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: TMDbLib
  dependency-version: 4.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 4, 2026
@karirafn
karirafn enabled auto-merge (rebase) November 4, 2026 22:38
…s to TMDbLib 4

TMDbLib 4 serializes through a source-generated context, so the tests use the TMDbLib Movie type instead of a private test type.
@karirafn
karirafn merged commit 5e06342 into main Nov 4, 2026
1 check passed
@karirafn
karirafn deleted the dependabot/nuget/main/nuget-e4b668284e branch November 4, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants