Repository navigation
Bump the nuget group with 6 updates - #435
Merged
Merged
Conversation
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>
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
DashboardPathinteractive, because the Blazor circuit never started._framework/Microsoft.NET.Sdk.BlazorWeb.DotNetWatch.<hash>.lib.module.js) to every Debug build of a Blazor host, even withoutdotnet watch. The dashboard's<base href>sends that request under the dashboard path, but the dashboard mirrored onlyblazor.web.jsandopaque-redirectthere. So the request failed, and the failed import stoppedBlazor.start._frameworktree under its path, forwarding each file to what the host serves at/_framework/./quartzpath, Release and publish builds, and builds with the .NET 10 SDK.FallbackPolicy.FallbackPolicythe dashboard recommends turned away every agent, even one with the right token.FallbackPolicy, whatever the hub's endpoint allows (dotnet/aspnetcore#69624). The compiler putsAsyncStateMachineAttributeon everyasyncmethod, so the agent hub'sRegisterwas held to the policy, and so were the live-events hub's methods.async, so they carry no attribute. The agent hub's own token check is unchanged.AllowAnonymous()under a fail-closedFallbackPolicydoesn't start its Blazor circuit on .NET 11 for an unauthenticated user. Blazor's ownStartCircuitmeets the same ASP.NET Core issue, which only ASP.NET Core can fix. (#4235, closes #4234)AddDeclaredJobs()is intercepted in anet11.0build.net11.0, aScheduleJoborAddJobdelegate in the sameAddQuartzlambda asAddDeclaredJobs()got no generated interceptor. It fell back to reflection binding, which a trimmed or native AOT app can't use.AddQuartzoverload.AddDeclaredJobs()is now intercepted too, which it never was before on any target framework. (#4235, closes #4234)typeandtitlefrom 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 thetypeandtitlethe HTTP API already wrote. (#4235, closes #4234)RunorRunAsyncstops itself once its stopping token fires. A second stop from elsewhere, such as an application's ownStopAsyncor a test host's dispose, then ranAttachedStoreDiscovery.StopAsyncat the same time. That threwInvalidOperationException: Collection was modified, even with no store attached. (#4230, closes #4229)The 3.x line gets the dashboard
_frameworkfix 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
NativeJobworks properly on Linux. There is no public API change and no schema change.Fixed
decimalcomes back as the number that was written. .NET 11 converts adoubleorfloatto thedecimalnearest its exact binary value, soJobDataMap.Get<decimal>of12.34dreturned12.339999999999999857891452848. Nothing threw, so a job reading an amount silently got a different number after the runtime upgrade. The values affected are adoubleorfloatin job data: untyped JSON numbers, scheduling data, the HTTP API, orPut("amount", 12.34). So are theDEC_PROP_1/2trigger columns, when a driver such as SQLite's returnsNUMERICas adouble. Quartz now rounds those to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4216, closes #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring, which .NET splits on whitespace, so/bin/sh -c echo hiranechoalone and the parameters never reached the command. (#4215, closes #4212)NativeJobkills the process tree. An interrupt or a shutdown left the child running, and the job reported the cancellation asError launching native command. The job now kills the process and its descendants, and ends as cancelled (OperationCanceledException) rather than failed. (#4215)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4215)Compatibility
NativeJobcommand 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 toParameters.NativeJobnow ends as cancelled rather than with aJobExecutionException. 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 stored typed job can be run now with its input. SQL Server joins lock-free firing rounds when
READ_COMMITTED_SNAPSHOTis on. An application on 4.6 compiles on 4.7 unchanged. One behaviour change needs checking:CronExpressionBuildernow writes0for 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.Highlights
SimpleScheduleBuilder.MeasureIntervalFromCompletion()starts the next run an interval after the previous one completes, so a long run never queues the next one behind it. TriggersUseDefaultTimeZone(Scheduler:DefaultTimeZone) gives its zone to every cron, calendar-interval, daily time-interval and recurrence trigger that names none. TriggersIScheduler.GetUpcomingFireTimescomputes 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. AConfigurationKeyvalue, or aQuartz:Scheduleexpression, interval or rule, of-leaves that trigger unscheduled and removes a stored copy. ConfigurationTriggerJob<TInput>(jobKey, input)fires anIJob<TInput>now with its input, and returns the trigger's key. TriggersREAD_COMMITTED_SNAPSHOTon and at least two live 4.7 nodes, a round of concurrent-allowed work takes no lock, and claims and fires in two transactions. ClusteringAddJsonTypeInfoResolverhands the scheduler yourJsonSerializerContextonce, for job data and for job inputs. Trimming and native AOTTriggers
MeasureIntervalFromCompletionon the builder, on[SimpleTrigger], in the JSON and XML schedules, through the HTTP API'supdate-detailsand in the dashboard's Edit details.QRTZ_TRIGGERS.FIXED_DELAY, from the required migration4.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.QuartzSchedulerOptions.DefaultTimeZone, orUseDefaultTimeZone(TimeZoneInfo). The keys areScheduler:DefaultTimeZoneandquartz.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'sTriggerKey, for history and fire-instance lookups.TriggerJob(jobKey, token)now compiles and fires the job with no data (#4150, closes #4138).CronExpressionBuilderleaves an unset seconds field at0, not*(#4144, closes #4143).WithMinuteIncrements(0, 5)used to build* 0/5 * ? * *, every second of every fifth minute. It now builds0 0/5 * ? * *. To fire every second, addWithSecondRange(0, 59).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
READ_COMMITTED_SNAPSHOTon and at least one other live 4.7 node. A single node keeps 4.5's rounds (reasonno_live_peer), because there they measured slower. Without the setting, rounds stay locked (reasonread_committed_snapshot_off, which replacessql_server). See SQL Server.FireInstance.InterruptRequestedUtcshows a pending request.UseTriggerGroupWhenUnset, not againstRECOVERING_JOBS(#4148, closes #4142). Also in 4.6.1.Dashboard and HTTP API
IQuartzApiClient.GetUpcomingFireTimes, a default interface member, from the routeGET …/triggers/{group}/{name}/fire-times. The agent operation isGetTriggerFireTimes. 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).Unregisterat 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
-switches a declared trigger off (#4151, closes #4137). It applies to aConfigurationKeyvalue, and to the JSON schedule'sCron.Expression,Simple.IntervalandRecurrence.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.MySQLfloorsMySqlConnectorat 2.6.1. 4.6.2 took the driver fromWeasel.MySql9.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 namesMySqlConnectoritself, at the first fixed version. An application that already references 2.6.1 or later is unaffected. (#4204, from #4197)TriggerJoblisted 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. OnRAMJobStoreit meant a walk of the whole store. Each firing not yet run made the next listing longer. A shipped delegate now readsEXECUTION_GROUPalone, and stops at the first row that settles the answer. On SQLite with 4,000 triggers,TriggerJobdrops from 38.6 ms to 12.4 ms. (#4204, from #4179 and #4174)Dependency change
Quartz.Weasel.MySQLgains a direct dependency onMySqlConnector(>= 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
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 asAsia/CalcuttaandEurope/Kiev, threwTimeZoneNotFoundExceptionthere. For those seven Windows ids, .NET maps through CLDR to the legacy names, which onlytzdata-legacyinstalls. Quartz now maps a legacy name to its canonical zone through tzdata 2026e'sbackwardlinks, and resolves it under the id asked for. The id a store writes toTIME_ZONE_IDtherefore does not depend on whether the host hastzdata-legacy. (#4180, from #4172)Behaviour change
UseTimeZoneConverteron such a host, 4.6.1 stored the canonical name (TimeZoneConverter 7.1.0 answersEurope/KyivforFLE 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.TimeZoneConverternow requires TimeZoneConverter 7.1.0; no other package's dependencies change.Fixed
AddTriggerandScheduleJobregistration and every scheduling file throughRescheduleJob. That resetTimesTriggered, so a finiteWithRepeatCountor a recurrence rule'sCOUNTran 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 ownRescheduleJobstill ends an individual pause. (#4147, from #4128)[DisallowConcurrentExecution]job's completion reads only the triggers that misfired. Each completion read every waiting trigger of the job in full underTRIGGER_ACCESSto 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)AddTypeInfoResolverwas stored, and then its job failed to load with Failed to parse JobDataMap from json. It now reads back as aDictionary<string, string>of its members: a number or a boolean as its JSON text ("3","true"), a nested object as its JSON, a null asnull. A map that 4.6.0 stored loads. (#4161, from #4156)UseTriggerGroupWhenUnset, a firing replayed after cluster recovery, a shutdown hand-back or startup recovery was limited underRECOVERING_JOBS, so it ran beside its group's live firings whatever the group's limit. (#4148, from #4142)CronTriggerImpl.Cloneshared the original's map, so a write through either was seen by both. The other trigger types already copied it. (#4160)Quartz.Plugins.TimeZoneConverterresolves seven more Windows ids on a system withouttzdata-legacy, such as Ubuntu 26.04: FLE, India, Argentina, Greenland, Myanmar, Nepal and US Eastern Standard Time. Their CLDR names are legacy links that onlytzdata-legacyinstalls, 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
JsonSerializationExceptionnames the entry, the type and the member. Such a value used to be stored and then fail to load. (#4161)IgnoreMisfirePolicytrigger as misfired. This applies to the completion of a[DisallowConcurrentExecution],BufferOneorCancelPreviousfiring, which also no longer writes such a trigger back. Acquisition fires it late, as the misfire handler andRAMJobStorealready 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_ACCESSlock, 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 warningQZ0007reports. 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.Highlights
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. ClusteringInterruptandInterruptFireInstancerecord a request for a firing on another node, and that node cancels the job's token after its next check-in.CancelPreviousnow works across nodes too. ClusteringExecutionHistoryOptions.WriteBehindIntervalset, a completion is queued and flushed with one status update per job per flush, at close to history-off throughput. Execution historyWithMisfireThresholdlets one trigger tolerate a longer delay, or a shorter one, without moving the store's threshold for every other trigger.DefaultMisfireHandlingsets what an unstated misfire instruction becomes, for every trigger type. TriggersPublishTrimmedandPublishAot.Quartz.Weasel.SQLitejoins the packages proven native on every pull request. Trimming and native AOTClustering
AdoJobStoreOptions.LockFreeFiringRounds, defaulttrue; flat keyquartz.jobStore.lockFreeFiringRounds.falserestores 4.5's rounds.QRTZ_SCHEDULER_STATE.QUARTZ_VERSION, from the required migration4.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).[DisallowConcurrentExecution]candidate, takes it.contention, event 3060) until the backlog clears or 2 s pass, so a drained backlog is no slower than under 4.5.INTERRUPT_REQUESTED_TIMEon the firing'sQRTZ_FIRED_TRIGGERSrow, from migration4.6/add_fired_trigger_interrupt. The node running the firing reads its requests after every check-in, so a request lands within oneCheckinInterval, 7.5 seconds by default.truefromInterruptmeans interrupted here or asked, not stopped.CancelPreviousasks a 4.6 peer instead of waiting asBufferOne. The two firings overlap for up to one check-in interval.UseClustering()used to leave every node atNON_CLUSTERED.Execution groups
IConfigurationkeep their case, and an execution-limit prefix such astenant:*can be configured (#4107, closes #4093).Execution history
ExecutionHistoryOptions.WriteBehindIntervalqueues each completion; one writer per store flushes every interval, or at 256 waiting runs, in one transaction with oneQRTZ_JOB_STATUSupdate per job. In the census, history on ran at 276 firings per second, write-behind at 379, and history off at 388.4.6/add_execution_history_lookup_indexes.Triggers
TriggerBuilder<TJob>.WithMisfireThreshold(TimeSpan),ITrigger.MisfireThreshold: positive, whole milliseconds;nullis the store'sMisfireThreshold, as before.[CronTrigger]/[SimpleTrigger]MisfireThreshold(checked by the new analyzer errorQZ0008), the JSON and XML schedules,TriggerDetailsUpdate, the HTTP API'supdate-detailsand 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.AgentrequiresMicrosoft.AspNetCore.SignalR.Client10.0.13. 4.5.0 required 10.0.0, and every SignalR client before 10.0.13 brings aMicrosoft.AspNetCore.SignalR.Commoncovered 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 forMicrosoft.Extensions.DependencyInjection,LoggingandLogging.Abstractions10.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 fromQuartz. (#4065)Quartz.Weasel.OracleandQuartz.Weasel.SqlServerrequireSystem.Security.Cryptography.Pkcs9.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.Dashboardin 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:
Newtonsoft.JsontoSystem.Text.JsonTmdbEntitybase, duplicate classes removed)Breaking changes:
Newtonsoft.Jsonneed to be migrated toSystem.Text.JsonWhat'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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 versionwill 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