Skip to content

chore(deps): Bump the nuget-dependencies group with 18 updates - #45

Merged
JerrettDavis merged 1 commit into
masterfrom
dependabot/nuget/nuget-dependencies-6d4df029ff
Sep 23, 2026
Merged

chore(deps): Bump the nuget-dependencies group with 18 updates#45
JerrettDavis merged 1 commit into
masterfrom
dependabot/nuget/nuget-dependencies-6d4df029ff

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 21, 2026

Copy link
Copy Markdown
Contributor

Updated Aspire.Hosting.PostgreSQL from 13.5.3 to 13.5.4.

Release notes

Sourced from Aspire.Hosting.PostgreSQL's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Updated Aspire.Hosting.Redis from 13.5.3 to 13.5.4.

Release notes

Sourced from Aspire.Hosting.Redis's releases.

13.5.4

What's New in Aspire 13.5.4

Patch release for Aspire 13.5 that fixes Kafka health-check resource leaks, DevTunnel errors with automatically selected regions, misleading Azure emulator dashboard entries, and unintended changes to generated starter apps, plus Homebrew compatibility and Radius API diagnostic updates.

🐛 Fixes

  • 📨 Kafka health checks leaked producers and polling threads — Each AppHost health-check execution created a new Kafka producer without disposing it, accumulating background threads over time. Health checks now reuse a producer per Kafka resource and dispose it with the AppHost, while keeping multiple Kafka resources independently configured. Fixes #​20091. (#​20094, backport of #​20092, @​davidfowl)

  • 🌐 DevTunnels could fail when the region was selected automatically — Tunnel setup and health checks now use the cluster-qualified tunnel ID returned by the DevTunnel CLI for port operations and access queries. This fixes failures when a bare tunnel ID cannot be resolved for those operations. Regression introduced in 13.3. Fixes #​18790. (#​19853, backport of #​19230, @​Vladipz)

  • ☁️ Emulator-only AppHosts showed an unused Azure environment — The dashboard now hides the azure-environment resource when no Azure resources require cloud provisioning, instead of leaving it visible in Not started. It remains visible for apps that combine local emulators with resources requiring Azure provisioning. No AppHost changes are needed. Fixes #​19617. (#​19998, backport of #​19843, @​eerhardt)

  • 🧩 Starter app generation could alter unrelated JavaScript values — Dynamic port replacement could also replace matching numeric literals in bundled JavaScript, including Bootstrap timing values. Port substitutions are now restricted to localhost: URLs, preserving the original library files while still configuring the requested ports. Fixes #​20030. (#​20110, backport of #​20031, @​bart-vmware, @​JamesNK)

  • 🍎 Updated the Aspire Homebrew cask for Homebrew 6.x — Replaced deprecated cask URL and post-install syntax with the supported equivalents, resolving compatibility issues with current Homebrew while preserving install-channel metadata. (#​20119, backport of #​19965, @​askpt, @​joperezr)

  • 🧪 Radius cloud-provider callback interfaces now carry the experimental diagnostic — IAwsRadiusProviderBuilder and IAzureRadiusProviderBuilder are now marked with ASPIRERADIUS003, matching the existing WithAwsProvider and WithAzureProvider methods. Code referencing these interfaces directly must now acknowledge the same experimental API diagnostic. (#​19874, @​sebastienros)

Full Changelog: v13.5.3...v13.5.4

Full commit: 9c1b401dd67746739044f68959cbf4d3d7af93a6

Commits viewable in compare view.

Updated FluentAssertions from 8.10.0 to 8.11.0.

Release notes

Sourced from FluentAssertions's releases.

8.11.0

What's Changed

New features

Improvements

Fixes

Documentation

Others

New Contributors

Full Changelog: fluentassertions/fluentassertions@8.10.0...8.11.0

Commits viewable in compare view.

Updated MessagePack from 3.1.8 to 3.1.9.

Release notes

Sourced from MessagePack's releases.

3.1.9

What's Changed

Security fix

Other fixes

Full Changelog: MessagePack-CSharp/MessagePack-CSharp@v3.1.8...v3.1.9

Commits viewable in compare view.

Updated MessagePack.Annotations from 3.1.8 to 3.1.9.

Release notes

Sourced from MessagePack.Annotations's releases.

3.1.9

What's Changed

Security fix

Other fixes

Full Changelog: MessagePack-CSharp/MessagePack-CSharp@v3.1.8...v3.1.9

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.10.0 to 18.10.1.

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

18.10.1

What's Changed

Full Changelog: microsoft/vstest@v18.10.0...v18.10.1

Commits viewable in compare view.

Updated MudBlazor from 9.9.0 to 9.10.0.

Release notes

Sourced from MudBlazor's releases.

9.10.0

What's Changed

New Features

Bug Fixes

Accessibility

Performance

Commits viewable in compare view.

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.18.0 to 1.19.0.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.19.0

For highlights and announcements pertaining to this release see: Release Notes > 1.19.0.

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0

... (truncated)

1.19.0-rc.1

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0-rc.1

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0-rc.1

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0-rc.1

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0-rc.1

    • Extended key/value list attribute handling to cover additional dictionary shapes (IEnumerable<KeyValuePair<string, string?>> and IDictionary). These attributes will be serialized as JSON objects.
      (#​7679)
      ... (truncated)

1.19.0-beta.1

The following changes are from the previous release 1.18.0-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusAspNetCoreTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • A scrape request whose connection is aborted, or whose X-Prometheus-Scrape-Timeout-Seconds deadline elapses, now stops waiting for an in-progress metrics collection instead of continuing to wait for it to finish. The collection itself is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusHttpListenerTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • Added PrometheusHttpListenerOptions.ScrapeResponseTimeoutMilliseconds (default 60000) which bounds how long a scrape request waits for its response. X-Prometheus-Scrape-Timeout-Seconds request header values may only shorten this limit. The limit bounds the request's wait only: a metrics collection already running when it is reached is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Shims.OpenTracing v1.19.0-beta.1

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.18.0 to 1.19.0.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.19.0

For highlights and announcements pertaining to this release see: Release Notes > 1.19.0.

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0

... (truncated)

1.19.0-rc.1

The following changes are from the previous release 1.18.0.

  • NuGet: OpenTelemetry v1.19.0-rc.1

    • Added Schema URL to internally created Resource instances.
      (#​7726)

    • Reduced allocations when formatting self-diagnostics events with up to three parameters.
      (#​7730)

    • Added AlwaysRecordSampler.
      (#​7695)

    • Fixed CircularBufferBuckets so the first delta histogram insertion after a reset does not result in an unnecessary scale reduction.
      (#​7749)

    • Improved wildcard source/meter name matching to avoid excessive matching time at runtime.
      (#​7760)

    • Fixed lazy logger provider builds after a failure from reusing partially initialized provider state.
      (#​7761)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api v1.19.0-rc.1

    • Reduced allocations when creating log record attributes from an array.
      (#​7699)

    • Reduced allocations when setting baggage through the params overload.
      (#​7697)

    • Reduced allocations when constructing SpanAttributes from an array.
      (#​7698)

    • Fixed parsing of an inbound tracestate header whose member value trimmed to an empty value that previously threw an IndexOutOfRangeException internally and could silently truncate the tracestate.
      (#​7756)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.19.0-rc.1

    No notable changes.

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Console v1.19.0-rc.1

    • Extended key/value list attribute handling to cover additional dictionary shapes (IEnumerable<KeyValuePair<string, string?>> and IDictionary). These attributes will be serialized as JSON objects.
      (#​7679)
      ... (truncated)

1.19.0-beta.1

The following changes are from the previous release 1.18.0-beta.1.

  • NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusAspNetCoreTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • A scrape request whose connection is aborted, or whose X-Prometheus-Scrape-Timeout-Seconds deadline elapses, now stops waiting for an in-progress metrics collection instead of continuing to wait for it to finish. The collection itself is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.19.0-beta.1

    • Breaking Change The PrometheusTranslationStrategy enum was renamed to PrometheusHttpListenerTranslationStrategy.
      (#​7751)

    • Fixed OpenMetrics _created series being emitted for metric points with a default start time.
      (#​7754)

    • Prometheus text/OpenMetrics escaping of label values, label names and help text is now more efficient.
      (#​7758)

    • Added PrometheusHttpListenerOptions.ScrapeResponseTimeoutMilliseconds (default 60000) which bounds how long a scrape request waits for its response. X-Prometheus-Scrape-Timeout-Seconds request header values may only shorten this limit. The limit bounds the request's wait only: a metrics collection already running when it is reached is not cancelled and continues running in the background.
      (#​7757)

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

  • NuGet: OpenTelemetry.Shims.OpenTracing v1.19.0-beta.1

    • Updated OpenTelemetry core component version(s) to 1.19.0.
      (#​7785)

    See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.AspNetCore from 1.18.0 to 1.19.0.

Release notes

Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.

1.19.0

1.19.0-rc.1

1.19.0-beta.1

1.19.0-alpha.1

1.18.1

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Http from 1.18.0 to 1.19.0.

Release notes

Sourced from OpenTelemetry.Instrumentation.Http's releases.

1.19.0

1.19.0-rc.1

1.19.0-beta.1

1.19.0-alpha.1

1.18.1

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Runtime from 1.18.0 to 1.19.0.

Release notes

Sourced from OpenTelemetry.Instrumentation.Runtime's releases.

1.19.0

1.19.0-rc.1

1.19.0-beta.1

1.19.0-alpha.1

1.18.1

Commits viewable in compare view.

Updated PatternKit.Core from 0.147.24 to 0.147.26.

Release notes

Sourced from PatternKit.Core's releases.

0.147.26

What's Changed

Full Changelog: JerrettDavis/PatternKit@v0.147.25...v0.147.26

0.147.25

What's Changed

Full Changelog: JerrettDavis/PatternKit@v0.147.24...v0.147.25

Commits viewable in compare view.

Updated Quartz from 4.0.1 to 4.1.1.

Release notes

Sourced from Quartz's releases.

4.1.1

Quartz.NET 4.1.1 is a maintenance release with one real bug in it: a scheduler that published traces produced one trace per process rather than one per firing, and it grew for as long as the process lived. Nothing about how a trigger fires changed, the schema is 4.0's, and the public API gained two overloads and lost nothing.

dotnet add package Quartz --version 4.1.1

What changed

  • A firing is a trace of its own again — subscribing to ActivitySource("Quartz") gave a single unbounded trace: every span the scheduler's loop opened became the parent of the next one, and each Quartz.Job.Execute hung off whichever was current when it was dispatched. A day of a quiet staging pod arrived at the backend as two trace ids and a tree several thousand spans deep, with the jobs' own EF Core and HttpClient spans buried under thousands of Quartz.JobStore.AcquireNextTriggers. The documentation has promised the opposite since 4.0 — the firing is its own trace root — and nothing tested it, because the observability suite reads tags off one span at a time and a span's parent is not a tag.

    Two independent defects made that trace, either sufficient on its own. The store decorator started its span in the synchronous override and stopped it inside the asynchronous continuation: Activity.Current is an AsyncLocal, so the start wrote onto the caller's execution context and the stop put the parent back onto the continuation's, which is discarded — leaving the caller with the span current for good, once per iteration of a loop that lives as long as the process. And the execute span took whatever activity was ambient as its parent, so merely starting the scheduler inside a request decided every firing's trace for the life of the application.

    Quartz.Job.Execute and Quartz.Job.Veto are now created with an empty parent context — so a parent-based sampler is asked about a root rather than about a context that is being discarded — with Activity.Current cleared around the start that re-reads it, and restored when the span stops. The store spans are started and stopped on one execution context. The three background loops — the scheduler thread, the cluster manager and the misfire handler — clear Activity.Current on entry, because their task captured the execution context of whoever called Start() and they outlive that call by the whole life of the process. Store spans still belong to whoever made the call, so scheduler.ScheduleJob(…) inside a request stays in that request's trace. (#​3797, #​3799)

    On the reporter's own repro, which expected 7 traces and 7 roots:

    traces largest trace executions trace roots
    4.1.0 2 30 spans 7 0
    4.1.1 31 1 span 7 7
    • Quartz.Job.Veto also gained the ActivityLink back to the call that scheduled the firing, which it never carried; a refused fire is now walked back from exactly as an executed one is.
    • The link is handed to CreateActivity rather than added after it. ActivityListener.Sample runs while the activity is created, so a link added afterwards was one no sampler ever saw — and sampling a consumer span by the trace that produced it is the reason links are given to samplers at all.
    • Behavior change worth noting: this is a change in the shape of what an exporter receives. A dashboard or saved query that searched for job executions by the trace they were nested in will not find them; they are roots. This is the documented behaviour finally arriving, not a new convention.

  • An execution limit or a job timeout can be read from the container — 4.x dropped the AddQuartz overloads that handed the callback an IServiceProvider, and the replacement the migration guide led with (read IConfiguration at registration time) bypasses Configure, PostConfigure and IValidateOptions. Everything else on IQuartzBuilder either lands in named options or has a Func<IServiceProvider, …> shape; UseExecutionLimits and AddJobTimeout computed their value eagerly and registered an internal type, so neither could be reached from the container at all. Both now have a shape that is handed one when the scheduler is built. Precedence is untouched — both shapes TryAdd, so the first declaration in code wins and code still beats the quartz.executionLimit.* keys. The migration guide now leads with the options pattern rather than with reading a section yourself, and names the caveat that made the old advice misfire: a scheduler's options are configured under its own name, so a bare AddOptions<T>() silently configures nothing of a named scheduler's. 3.x is unaffected — its four (configurator, IServiceProvider) overloads are still there. (#​3794, d523c898bc)

  • The documentation's dead links are fixed — the cron pages pointed at FreeFormatter.com, which is gone; they now answer with the library itself, and a handful of other rotted links across the 1.x–4.x trees were fixed with them. (#​3796)

Public API — two additions, nothing else

Added What it is
QuartzBuilderExtensions.AddJobTimeout(IQuartzBuilder, Func<IServiceProvider, TimeSpan?>) the default job timeout, computed once the container exists
QuartzBuilderExtensions.UseExecutionLimits(IQuartzBuilder, Action<IServiceProvider, ExecutionLimitsBuilder>) execution-group limits, configured with services in hand

v4.1.0..v4.1.1 baseline diff: 2 added lines, 0 removed. Every package's dependency list is byte-identical to 4.1.0 — the Microsoft.Extensions.* floors stay at 10.0.0, so an application pinned a servicing patch lower still restores.

One source-level wrinkle the second overload brings: AddJobTimeout(null) written with a literal null is now ambiguous between the two shapes. It means what AddJobTimeout() means; write that. Every other spelling — a TimeSpan, a TimeSpan? variable, the named-argument form, no argument at all — is unchanged, and UseExecutionLimits(null) is unaffected.

Upgrading

From 4.1.0: dotnet add package Quartz --version 4.1.1, and nothing else. There is no schema change, no configuration change, and no code change to make.

If you worked around #​3797 by leaving AddSource("Quartz") out and opening a root in an IJobExecutionMiddleware, you can drop the middleware and subscribe normally — and keep the Quartz.JobStore.* spans, which are now short traces of their own rather than noise in yours.

Full changelog: quartznet/quartznet@v4.1.0...v4.1.1

4.1.0

Quartz.NET 4.1 is an additive minor: every public change is a new type, a new member on a type we own, or a default interface member; the schema is 4.0's; a 4.0 application upgrades by changing the version. The headline is that a scheduler can now be added to, removed from and restarted in a running container — the one item the 4.0 roadmap deferred as "a 4.1 concern" — and around it the additive follow-ups filed during the 4.0 release candidates, an API reference for 4.x, and an honest Wolverine page now that Wolverine has a cron of its own.

dotnet add package Quartz --version 4.1.0

Highlights

  • Schedulers can be added, removed and restarted while the host runs — ISchedulerRuntime (it extends ISchedulerRegistry, as the 4.0 guide promised) builds a scheduler from a recipe into a container of its own that resolves the application's services, jobs and options from the application's container, binds it where the HTTP API, the dashboard and the health checks already look, drains it before it is replaced, and refuses the cases that cannot be made safe: a name the container registered, a bound name, a recipe that supplies an instance part, a restart whose drain gave up. ISchedulerFactory.LookupScheduler now builds a registered-but-unstarted scheduler on lookup. A restart builds the next generation first (a configuration error leaves the old one running), drains the old one within SchedulerRestartOptions.DrainTimeout (30 s by default) and only then initialises the new store — because the store's recovery sweep is per scheduler name, not per instance — and a drain that gives up leaves the name shut down and reported with no status until the next Restart finishes the job. A recipe that hands over a job store, thread pool, job factory or instance-id generator as an object is refused before anything is built, since a shut-down instance cannot be re-initialised. (#​3338; add/remove #​3725, restart #​3734)
  • Cron — MON/2 parses and means what 2/2 means (a step through the week, not 3.x's fortnight), and MON-FRI/2 is 2-6/2 where 4.0 silently read it as MON-FRI. (#​3732, #​3733 [85214e4499…e29f7c4283]). The century walk of CronCalendar.GetNextIncludedTimeUtc (#​3690) shipped in 4.0.1.
  • HTTP API — POST …/triggers/{group}/{name}/update-details edits a trigger in place (description, priority, job data, calendar, misfire instruction with its family, preferred node, execution group, retry policy; a field absent from the body is left alone and a null clears it), and HttpScheduler.UpdateTriggerDetails no longer throws — Context and ListenerManager are the two members a wire cannot carry (#​3681, #​3735). take says in the OpenAPI document why it is a string: a page size...

_Descri...

Description has been truncated

@dependabot
chore(deps): Bump the nuget-dependencies group with 18 updates
f41c219 
Bumps Aspire.Hosting.PostgreSQL from 13.5.3 to 13.5.4
Bumps Aspire.Hosting.Redis from 13.5.3 to 13.5.4
Bumps FluentAssertions from 8.10.0 to 8.11.0
Bumps MessagePack from 3.1.8 to 3.1.9
Bumps MessagePack.Annotations from 3.1.8 to 3.1.9
Bumps Microsoft.NET.Test.Sdk from 18.10.0 to 18.10.1
Bumps MudBlazor from 9.9.0 to 9.10.0
Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Extensions.Hosting from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Instrumentation.Http from 1.18.0 to 1.19.0
Bumps OpenTelemetry.Instrumentation.Runtime from 1.18.0 to 1.19.0
Bumps PatternKit.Core from 0.147.24 to 0.147.26
Bumps Quartz from 4.0.1 to 4.1.1
Bumps Quartz.AspNetCore from 4.0.1 to 4.1.1
Bumps TinyBDD from 0.19.39 to 0.19.40
Bumps TinyBDD.Xunit from 0.19.39 to 0.19.40
Bumps WireMock.Net from 2.15.0 to 2.16.0

---
updated-dependencies:
- dependency-name: Aspire.Hosting.PostgreSQL
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Aspire.Hosting.Redis
  dependency-version: 13.5.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: FluentAssertions
  dependency-version: 8.11.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: MessagePack
  dependency-version: 3.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: MessagePack.Annotations
  dependency-version: 3.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.10.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: MudBlazor
  dependency-version: 9.10.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Extensions.Hosting
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Instrumentation.AspNetCore
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Instrumentation.Http
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Instrumentation.Runtime
  dependency-version: 1.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: PatternKit.Core
  dependency-version: 0.147.26
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Quartz
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: Quartz.AspNetCore
  dependency-version: 4.1.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: TinyBDD
  dependency-version: 0.19.40
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: TinyBDD.Xunit
  dependency-version: 0.19.40
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: WireMock.Net
  dependency-version: 2.16.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@JerrettDavis
JerrettDavis merged commit c045e78 into master Sep 23, 2026
13 checks passed
@JerrettDavis
JerrettDavis deleted the dependabot/nuget/nuget-dependencies-6d4df029ff branch September 23, 2026 05:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment