Skip to content

Bump the nuget-dependencies group with 18 updates - #568

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-dependencies-f5afaf4046
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/dot-config/nuget-dependencies-f5afaf4046

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Updated dotnet-stryker from 5.0.0 to 5.1.0.

Release notes

Sourced from dotnet-stryker's releases.

5.1.0

5.1.0 (2026-11-10)

Bug Fixes

Features

Performance Improvements

  • test-runner: materialize executed identifiers once per result (#​3929) (6a2513a)

Commits viewable in compare view.

Updated Microsoft.AspNetCore.TestHost from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.AspNetCore.TestHost's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.EntityFrameworkCore.Sqlite from 10.0.14 to 10.0.15.

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.Caching.StackExchangeRedis from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Caching.StackExchangeRedis's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Configuration.Binder from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Configuration.Binder's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.Extensions.Hosting from 10.0.14 to 10.0.15.

Release notes

Sourced from Microsoft.Extensions.Hosting's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.NET.Test.Sdk from 18.11.0 to 18.11.1.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.AspNetCore from 1.20.1 to 1.20.2.

Release notes

Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.

1.20.2

1.20.2-beta.1

  • NuGet: OpenTelemetry.Instrumentation.Hangfire v1.20.2-beta.1

    • Fixed failed jobs exporting the exception message as the span status description.
      The message is now only recorded when RecordException is enabled.
      (#​5884)

    • Fixed baggage from a job being visible to work started by other jobs
      performed on the same worker.
      (#​5886)

    • Added EnrichWithBackgroundJob and CustomStateMappings to
      HangfireMetricsInstrumentationOptions. Use them to add custom attributes to
      the metrics and to count jobs in custom Hangfire states.
      (#​5810)

    • Fixed workflow.execution.duration for the executing state. It included the
      time of other measurements of this instrumentation, for example the database
      query that RecordQueueLatency adds.
      (#​5810)

    See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.Http from 1.20.1 to 1.20.2.

Release notes

Sourced from OpenTelemetry.Instrumentation.Http's releases.

1.20.2

1.20.2-beta.1

  • NuGet: OpenTelemetry.Instrumentation.Hangfire v1.20.2-beta.1

    • Fixed failed jobs exporting the exception message as the span status description.
      The message is now only recorded when RecordException is enabled.
      (#​5884)

    • Fixed baggage from a job being visible to work started by other jobs
      performed on the same worker.
      (#​5886)

    • Added EnrichWithBackgroundJob and CustomStateMappings to
      HangfireMetricsInstrumentationOptions. Use them to add custom attributes to
      the metrics and to count jobs in custom Hangfire states.
      (#​5810)

    • Fixed workflow.execution.duration for the executing state. It included the
      time of other measurements of this instrumentation, for example the database
      query that RecordQueueLatency adds.
      (#​5810)

    See CHANGELOG for details.

Commits viewable in compare view.

Updated Oracle.EntityFrameworkCore from 10.23.26301 to 10.23.26400.

Updated Oracle.ManagedDataAccess.Core from 23.26.301 to 23.26.400.

Updated Quartz from 3.22.9 to 3.22.10.

Release notes

Sourced from Quartz's releases.

3.22.10

11 fixes for the 3.x line. There is no public API change and no schema change.

Fixed

  • The dashboard's Save schedule reports an invalid cron expression as invalid. Saving an expression that does not parse replaced the trigger page with Failed to parse ITrigger from json and a Retry button. It now shows Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @​EnesKartal. (#​4190, closes #​4188)
  • Saving a cron schedule from the dashboard keeps the trigger on its schedule. Save schedule sent the trigger's original start back, so for a trigger that had been scheduled a while the next fire came out in the past. The scheduler treated the trigger as misfired and ran it once off its schedule. A start that has passed now moves to the whole second after the save, and the Upcoming cron fires preview follows the same rule. Thanks @​mkokkerametla for the report and @​EnesKartal for the analysis. (#​4256, closes #​4187)
  • A CronTriggerImpl clone has a job data map of its own. It used MemberwiseClone rather than the base clone that every other trigger type uses, so the clone shared the original's JobDataMap. RAMJobStore stores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#​4205)
  • Recovery of a replay keeps the firing it replays. When a recovery firing was itself recovered, startup recovery and cluster recovery overwrote the FailedJobOriginalTrigger* markers. IJobExecutionContext.RecoveringTriggerKey then named the spent recovery trigger (RECOVERING_JOBS.recover_…) instead of the original trigger, and the fire-time markers named the first replay's times. Both paths now keep the markers the recovery trigger already carries. (#​4205)
  • On .NET 11, a trigger's decimal property keeps its value. .NET 11 converts a double to the decimal nearest its exact binary value. So when a driver returns the DEC_PROP_1/2 columns as a double, as SQLite's does, 12.34 came back as 12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4219, from #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string that .NET splits on whitespace, so the parameters never reached the command. (#​4220, from #​4212)
  • Cancelling a waiting NativeJob kills the process tree, and the job ends as cancelled rather than with Error launching native command. (#​4220)
  • NativeJob reads output without foreground threads, so a child that holds its pipes open no longer keeps the host alive after shutdown. All output is still logged before the job completes, unless a process the command started holds the streams open more than 5 seconds after it exits. (#​4220)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4220)
  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK. The SDK adds a hot-reload JS initializer to every Debug build of a Blazor host. The dashboard's <base href> sent it under the dashboard path, where only blazor.web.js and opaque-redirect were mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole _framework tree under its path. Thanks to the Marten Studio maintainers for the report. (#​4227, from #​4224)
  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or check-in commit now goes through its validator and retry as it does on other databases, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @​mrreddevil2412. (#​4261, from #​4255)

Packaging

Quartz.Jobs gains a net8.0 build, which .NET 8 and later now pick up instead of netstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. The netstandard2.0 and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the other NativeJob changes.

Compatibility

On Linux with .NET 8 or later, 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.

The integration tests move to MySqlConnector 2.6.1, the first version fixed for GHSA-473q-m89c-ghf8 (#​4198). No 3.x package references the driver.

What's Changed

Fixes

Other changes

New Contributors

Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10

Commits viewable in compare view.

Updated Quartz.Extensions.DependencyInjection from 3.22.9 to 3.22.10.

Release notes

Sourced from Quartz.Extensions.DependencyInjection's releases.

3.22.10

11 fixes for the 3.x line. There is no public API change and no schema change.

Fixed

  • The dashboard's Save schedule reports an invalid cron expression as invalid. Saving an expression that does not parse replaced the trigger page with Failed to parse ITrigger from json and a Retry button. It now shows Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @​EnesKartal. (#​4190, closes #​4188)
  • Saving a cron schedule from the dashboard keeps the trigger on its schedule. Save schedule sent the trigger's original start back, so for a trigger that had been scheduled a while the next fire came out in the past. The scheduler treated the trigger as misfired and ran it once off its schedule. A start that has passed now moves to the whole second after the save, and the Upcoming cron fires preview follows the same rule. Thanks @​mkokkerametla for the report and @​EnesKartal for the analysis. (#​4256, closes #​4187)
  • A CronTriggerImpl clone has a job data map of its own. It used MemberwiseClone rather than the base clone that every other trigger type uses, so the clone shared the original's JobDataMap. RAMJobStore stores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#​4205)
  • Recovery of a replay keeps the firing it replays. When a recovery firing was itself recovered, startup recovery and cluster recovery overwrote the FailedJobOriginalTrigger* markers. IJobExecutionContext.RecoveringTriggerKey then named the spent recovery trigger (RECOVERING_JOBS.recover_…) instead of the original trigger, and the fire-time markers named the first replay's times. Both paths now keep the markers the recovery trigger already carries. (#​4205)
  • On .NET 11, a trigger's decimal property keeps its value. .NET 11 converts a double to the decimal nearest its exact binary value. So when a driver returns the DEC_PROP_1/2 columns as a double, as SQLite's does, 12.34 came back as 12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4219, from #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string that .NET splits on whitespace, so the parameters never reached the command. (#​4220, from #​4212)
  • Cancelling a waiting NativeJob kills the process tree, and the job ends as cancelled rather than with Error launching native command. (#​4220)
  • NativeJob reads output without foreground threads, so a child that holds its pipes open no longer keeps the host alive after shutdown. All output is still logged before the job completes, unless a process the command started holds the streams open more than 5 seconds after it exits. (#​4220)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4220)
  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK. The SDK adds a hot-reload JS initializer to every Debug build of a Blazor host. The dashboard's <base href> sent it under the dashboard path, where only blazor.web.js and opaque-redirect were mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole _framework tree under its path. Thanks to the Marten Studio maintainers for the report. (#​4227, from #​4224)
  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or check-in commit now goes through its validator and retry as it does on other databases, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @​mrreddevil2412. (#​4261, from #​4255)

Packaging

Quartz.Jobs gains a net8.0 build, which .NET 8 and later now pick up instead of netstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. The netstandard2.0 and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the other NativeJob changes.

Compatibility

On Linux with .NET 8 or later, 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.

The integration tests move to MySqlConnector 2.6.1, the first version fixed for GHSA-473q-m89c-ghf8 (#​4198). No 3.x package references the driver.

What's Changed

Fixes

Other changes

New Contributors

Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10

Commits viewable in compare view.

Updated Quartz.Extensions.Hosting from 3.22.9 to 3.22.10.

Release notes

Sourced from Quartz.Extensions.Hosting's releases.

3.22.10

11 fixes for the 3.x line. There is no public API change and no schema change.

Fixed

  • The dashboard's Save schedule reports an invalid cron expression as invalid. Saving an expression that does not parse replaced the trigger page with Failed to parse ITrigger from json and a Retry button. It now shows Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @​EnesKartal. (#​4190, closes #​4188)
  • Saving a cron schedule from the dashboard keeps the trigger on its schedule. Save schedule sent the trigger's original start back, so for a trigger that had been scheduled a while the next fire came out in the past. The scheduler treated the trigger as misfired and ran it once off its schedule. A start that has passed now moves to the whole second after the save, and the Upcoming cron fires preview follows the same rule. Thanks @​mkokkerametla for the report and @​EnesKartal for the analysis. (#​4256, closes #​4187)
  • A CronTriggerImpl clone has a job data map of its own. It used MemberwiseClone rather than the base clone that every other trigger type uses, so the clone shared the original's JobDataMap. RAMJobStore stores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#​4205)
  • Recovery of a replay keeps the firing it replays. When a recovery firing was itself recovered, startup recovery and cluster recovery overwrote the FailedJobOriginalTrigger* markers. IJobExecutionContext.RecoveringTriggerKey then named the spent recovery trigger (RECOVERING_JOBS.recover_…) instead of the original trigger, and the fire-time markers named the first replay's times. Both paths now keep the markers the recovery trigger already carries. (#​4205)
  • On .NET 11, a trigger's decimal property keeps its value. .NET 11 converts a double to the decimal nearest its exact binary value. So when a driver returns the DEC_PROP_1/2 columns as a double, as SQLite's does, 12.34 came back as 12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4219, from #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string that .NET splits on whitespace, so the parameters never reached the command. (#​4220, from #​4212)
  • Cancelling a waiting NativeJob kills the process tree, and the job ends as cancelled rather than with Error launching native command. (#​4220)
  • NativeJob reads output without foreground threads, so a child that holds its pipes open no longer keeps the host alive after shutdown. All output is still logged before the job completes, unless a process the command started holds the streams open more than 5 seconds after it exits. (#​4220)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4220)
  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK. The SDK adds a hot-reload JS initializer to every Debug build of a Blazor host. The dashboard's <base href> sent it under the dashboard path, where only blazor.web.js and opaque-redirect were mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole _framework tree under its path. Thanks to the Marten Studio maintainers for the report. (#​4227, from #​4224)
  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or check-in commit now goes through its validator and retry as it does on other databases, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @​mrreddevil2412. (#​4261, from #​4255)

Packaging

Quartz.Jobs gains a net8.0 build, which .NET 8 and later now pick up instead of netstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. The netstandard2.0 and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the other NativeJob changes.

Compatibility

On Linux with .NET 8 or later, 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.

The integration tests move to MySqlConnector 2.6.1, the first version fixed for GHSA-473q-m89c-ghf8 (#​4198). No 3.x package references the driver.

What's Changed

Fixes

Other changes

New Contributors

Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10

Commits viewable in compare view.

Updated Quartz.Serialization.SystemTextJson from 3.22.9 to 3.22.10.

Release notes

Sourced from Quartz.Serialization.SystemTextJson's releases.

3.22.10

11 fixes for the 3.x line. There is no public API change and no schema change.

Fixed

  • The dashboard's Save schedule reports an invalid cron expression as invalid. Saving an expression that does not parse replaced the trigger page with Failed to parse ITrigger from json and a Retry button. It now shows Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @​EnesKartal. (#​4190, closes #​4188)
  • Saving a cron schedule from the dashboard keeps the trigger on its schedule. Save schedule sent the trigger's original start back, so for a trigger that had been scheduled a while the next fire came out in the past. The scheduler treated the trigger as misfired and ran it once off its schedule. A start that has passed now moves to the whole second after the save, and the Upcoming cron fires preview follows the same rule. Thanks @​mkokkerametla for the report and @​EnesKartal for the analysis. (#​4256, closes #​4187)
  • A CronTriggerImpl clone has a job data map of its own. It used MemberwiseClone rather than the base clone that every other trigger type uses, so the clone shared the original's JobDataMap. RAMJobStore stores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#​4205)
  • Recovery of a replay keeps the firing it replays. When a recovery firing was itself recovered, startup recovery and cluster recovery overwrote the FailedJobOriginalTrigger* markers. IJobExecutionContext.RecoveringTriggerKey then named the spent recovery trigger (RECOVERING_JOBS.recover_…) instead of the original trigger, and the fire-time markers named the first replay's times. Both paths now keep the markers the recovery trigger already carries. (#​4205)
  • On .NET 11, a trigger's decimal property keeps its value. .NET 11 converts a double to the decimal nearest its exact binary value. So when a driver returns the DEC_PROP_1/2 columns as a double, as SQLite's does, 12.34 came back as 12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#​4219, from #​4210)
  • NativeJob passes its parameters to the shell on Linux. The command and its parameters were joined into one Arguments string that .NET splits on whitespace, so the parameters never reached the command. (#​4220, from #​4212)
  • Cancelling a waiting NativeJob kills the process tree, and the job ends as cancelled rather than with Error launching native command. (#​4220)
  • NativeJob reads output without foreground threads, so a child that holds its pipes open no longer keeps the host alive after shutdown. All output is still logged before the job completes, unless a process the command started holds the streams open more than 5 seconds after it exits. (#​4220)
  • NativeJob runs the system directory's cmd.exe on Windows, never one that PATH or the working directory finds first. (#​4220)
  • A dashboard at a custom path loads in a Debug build made with the .NET 11 SDK. The SDK adds a hot-reload JS initializer to every Debug build of a Blazor host. The dashboard's <base href> sent it under the dashboard path, where only blazor.web.js and opaque-redirect were mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole _framework tree under its path. Thanks to the Marten Studio maintainers for the report. (#​4227, from #​4224)
  • On PostgreSQL, a failed commit is reported as itself. Npgsql throws ObjectDisposedException when asked for the connection of a transaction its broken connector disposed. The store's disconnected-transaction check let that escape in place of the real error, from rollbacks, row-lock retries and the enlisted-transaction checks. A failed fire-batch or check-in commit now goes through its validator and retry as it does on other databases, and the cluster manager no longer logs Error managing cluster: NpgsqlTransaction. Thanks @​mrreddevil2412. (#​4261, from #​4255)

Packaging

Quartz.Jobs gains a net8.0 build, which .NET 8 and later now pick up instead of netstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. The netstandard2.0 and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the other NativeJob changes.

Compatibility

On Linux with .NET 8 or later, 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.

The integration tests move to MySqlConnector 2.6.1, the first version fixed for GHSA-473q-m89c-ghf8 (#​4198). No 3.x package references the driver.

What's Changed

Fixes

Other changes

New Contributors

Full Changelog: quartznet/quartznet@v3.22.9...v3.22.10

Commits viewable in compare view.

Updated System.Security.Cryptography.Pkcs from 10.0.14 to 10.0.15.

Release notes

Sourced from System.Security.Cryptography.Pkcs's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated WolverineFx from 6.53.0 to 6.64.0.

Release notes

Sourced from WolverineFx's releases.

6.64.0

A small release: three fixes, one of them a new observer signal, and a JasperFx and Weasel bump. JasperFx moves from 2.100.1 to 2.102.0 and Weasel from 9.49.0 to 9.50.0; Marten (9.58.0), Polecat (5.49.0) and Fisher (1.28.0) are unchanged. There is no schema change and no breaking API change.

Fixes

  • Native-ack listeners: on a group-partitioned NativeAck endpoint, an envelope settled before it reached a handler (an unknown message type, an unreadable payload) is released from the lease tracker and the in-memory idempotency guard. It used to stay tracked until the lease ceiling and then log a false "unsettled for 00:59:xx" warning, an hour after it was completed (GH-5443).
  • Circuit breakers: IWolverineObserver.CircuitBreakerReset is now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened on CircuitBreakerTripped could never be closed by Wolverine's own signal. A new overload, CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own after PauseTime or through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).
  • Rabbit MQ: ResetResourceState() no longer adds a new wolverine.response.* queue on every call. Each reset had been declaring and purging every reply queue built so far, so a test suite that resets before each test slowed down with every test, and a sender started after a reset could send its replies to a queue nobody listened to, so InvokeAsync<T>() timed out (GH-5452, thanks to @​alesdvorakcz).

Docs

  • The command line runs from a Native AOT binary since JasperFx 2.101.0 (#​5442).
  • The resource setup hosted service migrates message storage regardless of AutoCreate (#​5445).

What's Changed

Full Changelog: JasperFx/wolverine@V6.63.0...V6.64.0

6.63.0

This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.

Fixes

  • Envelope ids: default envelope ids no longer collide between processes on one machine. Collisions showed up as inbox duplicate-key errors and silently dropped "duplicate" deliveries (#​5399).
  • Stale nodes: a node that resumes after being ejected as stale does not commit work another node already handled (GH-5423), and Oracle's in-transaction mark-as-handled refuses that work too (GH-5429).
  • Ambiguous commits: a commit that applied but reported an error is no longer dead-lettered, and its cascading messages run (GH-5410).
  • Database queues:
    • scheduled retries are atomic on SQL Server, MySQL, Oracle and SQLite (#​5408), and fenced on the inbox row's owner on every store (GH-5426);
    • the outbox-to-queue move is one transaction on MySQL, SQL Server and SQLite (GH-5438);
    • a durable pop skips envelopes the inbox already holds instead of rolling the whole batch back (GH-5411);
    • a backlog drains without waiting a polling interval per batch (GH-5413).
  • SQL Server: the scheduled-message poll never waits on a lock (GH-5412).
  • MySQL: the expired-handled cleanup no longer locks live inbox rows (GH-5428).
  • SQLite: Balanced mode assigns node numbers and reads health checks as UTC (GH-5430).
  • Multi-tenancy: tenant databases with the same name on one host are told apart by port, so each gets its own durability agent (GH-5435).
  • Dead letters: a dead letter marked replayable mid-move is no longer deleted before it reaches the inbox (GH-5395).
  • Interop: CloudEvents and MassTransit interop keep the inbox id of a durable envelope when they read the message id (#​5396, thanks to @​lahma; #​5398).
  • HTTP: span tags are written before anything can short-circuit the request (GH-5406).
  • Testing: a tracked session no longer completes while a handler's cascading messages are still running (#​5400, thanks to new contributor @​haefele-octoja).

Docs

  • Schema management options for message storage, linked to Weasel and the stateful resource model (#​5437).
  • Waiting on a message the broker fans out to several queues (GH-5416).
  • The durability chaos rig has a README covering its roles, CHAOS_* knobs and containers (GH-5409, GH-5414).

What's Changed

6.62.0

This is a minor release on JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0 and Fisher 1.28.0. Upgrading is a package bump: there is no schema change and no breaking API change. If your projects pin JasperFx.Events.SourceGenerator centrally, pin it to the same version as JasperFx.Events (see the note at the end).

New

  • Sagas: [SagaIsResponseOnly] for an endpoint that returns a saga as its response (GH-5069).
  • PostgreSQL: PublishOnlyToShardedPostgresqlQueues, for publishing to sharded queues with no listeners (GH-5088).
  • EF Core: the transactional middleware's isolation level is configurable (GH-5207).
  • Azure Service Bus: support for externally owned topics (GH-5342).
  • HTTP:
    • a ProblemDetails factory for the 409 conflict mapping (GH-5353);
    • an AggregateException of concurrency failures maps to 409 (GH-5355);
    • OpenAPI describes query, header and form parameters with their data annotations;
    • [DeduplicatedWithResponse] replays ASP.NET Core IResult responses, and reads a replayed Location without per-request reflection (GH-5381).
  • Kafka: the replay group id can be set, with a kafka-replay --group-id option (thanks to new contributor @​Mr444-dev).
  • Testing:
    • WhenTracked sees events an application commits through its own injected IDocumentSession, on Marten, Polecat and Fisher (GH-5385, GH-5390);
    • GenerationRules.ReuseCompiledAssemblies (JasperFx 2.100.0) is documented and tested for many hosts in one process, in Dynamic and Auto modes, the codegen command and HTTP chains (GH-5378, GH-5391).
  • Event Model: EventModelReport prints the decider line beside starts (GH-5379), and scaffold turns a multi-event automation into one handler class (GH-5361).

Fixes

  • Local queues: buffered and durable local queues whose receiving block faulted are rebuilt (GH-5358), and DurableLocalQueue.StartAsync skips an already accepting queue and is serialized (GH-5348).
  • Inbox recovery into an inline endpoint with ListenerCount > 1 no longer recurses forever (GH-5363).
  • Middleware: an OnException returning a tuple generates code that compiles (GH-5356), and OnException handlers for the same exception type merge into one catch clause.
  • CloudEvents: CloudEventsMapper keeps the envelope id on re-read, with a stable id for non-Guid CloudEvent ids (GH-5364).
  • PostgreSQL: the scheduled-message poll gets the index SQL Server already had (GH-5346).
  • Scaffold no longer plans every emitted event as an Apply on every stream (GH-5360, a partial fix; the rest stays open).
  • Build: NU1903 (GHSA-p3jp-9v83-76w9) on Microsoft.DotNet.ILCompiler is cleared (GH-5387).

Pinning JasperFx centrally

Polecat 5.49.0 needs JasperFx 2.100.1. If JasperFx.Events is lifted to 2.100.1 while JasperFx.Events.SourceGenerator stays pinned at 2.100.0, the generator emits nothing and projections fail at run time with "No source-generated dispatcher found". Keep the two on one version (jasperfx#​1138).

What's Changed

6.61.0

This is a minor release. Upgrading is a package bump only: there is no schema change and no breaking API change.

New

  • GH-5320 (#​5326): Recurring schedules can now run as often as every second, and a schedule can skip an occurrence while the previous one is still running.
    • CronSchedule.MinimumCadence is now one second, for six-field cron expressions such as * * * * * *. Anything faster than five seconds always runs on a timer agent, and UseScheduledMessages() refuses it.
    • The new SkipWhileRunning() on a recurring schedule invokes each occurrence instead of publishing it. An occurrence that comes due while the previous one is still running is skipped, and skipped occurrences are not made up later. Skips are logged and counted in the new wolverine-recurring-occurrences-skipped metric.
    • With a local handler, the occurrence runs on the node that owns the schedule's timer agent, so overlap is prevented across the cluster. Because the occurrence is invoked, other subscribers don't receive it, and it has no inbox row, queue error policy or dead letter queue. A failed occurrence is logged and the next one runs on schedule. With a handler on another node, the wait is capped at 5 seconds.
    • A one-second schedule writes about 86,400 deduplication rows a day.
  • GH-5317 (#​5323): PauseThenCatchUpOnAllMartenDaemonActivityAsync() and the tracked-session option PauseThenCatchUpOnAllMartenDaemonActivity() catch up the main Marten store and every ancillary store registered with IntegrateWithWolverine() in one call. A store with no events is skipped.
  • GH-5311 (#​5324): A failed handler attempt now records the OpenTelemetry exception event (exception.type, exception.message, exception.stacktrace) on its span, instead of only the exception's type name. Exception messages can carry application data, so you can turn this off with opts.Tracking.RecordExceptionsOnSpans = false.
  • GH-5339 (#​5341): EntityDescriptor.Ddl now carries each EF Core entity's CREATE TABLE script, with its keys, foreign keys and indexes, the same way DocumentMappingDescriptor.Ddl does for documents. It's generated from the model, so no connection is opened, and it's the model's script rather than the database's. Non-relational providers and view-mapped entities leave it empty. Needs JasperFx 2.99.0.
  • GH-5332 (#​5338): Wolverine HTTP endpoints now tag the request span with http.route and http.request.method, the OpenTelemetry semantic convention names, alongside handler.type. Both are constants in the generated code. Pre-generated code should be regenerated.
  • Dead letter queries can filter their time range on the failure time with the new DeadLetterEnvelopeQuery.RangeOn (DeadLetterTimeField.SentAt or FailedAt) (#​5330). FailedAt falls back to sent_at when failed_at is null, and applies to query, replay, discard and archive. The default stays SentAt. Supported by the PostgreSQL, SQL Server, MySQL, SQLite, Oracle, CosmosDb and RavenDb stores.

Fixes

  • GH-5310 (#​5328): With Marten's TrackConnections turned on, the handler, saga and stream tags (handler.type, message.handler, wolverine.saga.*, wolverine.stream.*) landed on the marten.connection span instead of the message's own span. They now stay on the message span, and on the request span for HTTP endpoints. Pre-generated code should be regenerated.
  • GH-5312 (#​5327): A durable ScheduleRetry(...) lost the link to the attempt that failed, because the stored envelope body wasn't rewritten when the retry was scheduled. Every message store now rewrites the body when it reschedules an envelope.
  • GH-5313 (#​5321): Azure Service Bus queues and subscriptions and Amazon SQS queues now report DeadLetterStorageMode.NativeWithRecovery when EnableDeadLetterQueueRecovery() drains them, so CritterWatch's startup check no longer warns about them.
  • GH-5314 (#​5325): With RabbitMQ's EnableDeadLetterQueueRecovery(), stopping the host could throw AlreadyClosedException when two stops ran at once, as they do under WebApplicationFactory. Stopping the dead letter queue listener is now idempotent and never throws.
  • GH-5315 (#​5322): FindSingleTrackedMessageOfType<T>() now counts envelopes rather than distinct message values, so publishing two equal records fails the check. A message sent to several destinations still counts once. Use tracked.Sent.SingleMessage<T>() for a check per destination.
  • GH-5318 (#​5319): The testing docs now explain that the pause in PauseThenCatchUpOnMartenDaemonActivity waits out the high water agent's current poll tick. The fix is JasperFx/jasperfx#​1100.
  • GH-5331 (#​5336): With runtime code generation, each saga message disappeared from ServiceCapabilities.Sagas once it had been handled, and the saga disappeared once every message had been. The saga report, including each store's GetRegisteredSagasAsync, now reads the same before and after the chains compile.
  • GH-5334 (#​5337): In Balanced mode, lifting a pause on a URI that no agent owns, such as a listening endpoint, waited out AgentRestrictionConfirmationTimeout and then threw AgentRestrictionsNotConfirmedException. It now returns at once. Agent URIs are still confirmed as before.
  • Sessions the application opens itself and enrolls with IPolecatOutbox.Enroll or IFisherOutbox.Enroll never flushed their outgoing messages on commit (#​5309). Durable messages waited until a restart and buffered messages were lost. They now flush on commit, the same as handler sessions, and the incoming envelope is marked handled once instead of twice.

Dependencies

  • JasperFx 2.99.0 (#​5333 took 2.98.0, #​5341 2.99.0).
  • Weasel 9.48.0 and MySqlConnector 2.6.1 (#​5335). MySqlConnector 2.6.1 closes GHSA-473q-m89c-ghf8 for WolverineFx.MySql. On SQL Server, a DateTime parameter in a message store command now goes out as datetime2 instead of datetime. Every envelope time column is datetimeoffset, so no column is converted either way.

Thanks to @​uniquelau for #​5313, #​5314, #​5315, #​5317 and #​5318, and to @​lahma for #​5330.

Full Changelog: https://github.com/JasperFx/w...

Description has been truncated

Bumps dotnet-stryker from 5.0.0 to 5.1.0
Bumps Microsoft.AspNetCore.TestHost from 10.0.14 to 10.0.15
Bumps Microsoft.EntityFrameworkCore.Sqlite from 10.0.14 to 10.0.15
Bumps Microsoft.Extensions.Caching.StackExchangeRedis from 10.0.14 to 10.0.15
Bumps Microsoft.Extensions.Configuration.Binder from 10.0.14 to 10.0.15
Bumps Microsoft.Extensions.Hosting from 10.0.14 to 10.0.15
Bumps Microsoft.NET.Test.Sdk from 18.11.0 to 18.11.1
Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.20.1 to 1.20.2
Bumps OpenTelemetry.Instrumentation.Http from 1.20.1 to 1.20.2
Bumps Oracle.EntityFrameworkCore from 10.23.26301 to 10.23.26400
Bumps Oracle.ManagedDataAccess.Core from 23.26.301 to 23.26.400
Bumps Quartz from 3.22.9 to 3.22.10
Bumps Quartz.Extensions.DependencyInjection from 3.22.9 to 3.22.10
Bumps Quartz.Extensions.Hosting from 3.22.9 to 3.22.10
Bumps Quartz.Serialization.SystemTextJson from 3.22.9 to 3.22.10
Bumps System.Security.Cryptography.Pkcs from 10.0.14 to 10.0.15
Bumps WolverineFx from 6.53.0 to 6.64.0
Bumps WolverineFx.RabbitMQ from 6.53.0 to 6.64.0

---
updated-dependencies:
- dependency-name: dotnet-stryker
  dependency-version: 5.1.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.AspNetCore.TestHost
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.EntityFrameworkCore.Sqlite
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.Extensions.Caching.StackExchangeRedis
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.Extensions.Configuration.Binder
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.Extensions.Hosting
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.NET.Test.Sdk
  dependency-version: 18.11.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Instrumentation.AspNetCore
  dependency-version: 1.20.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: OpenTelemetry.Instrumentation.Http
  dependency-version: 1.20.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Oracle.EntityFrameworkCore
  dependency-version: 10.23.26400
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Oracle.ManagedDataAccess.Core
  dependency-version: 23.26.400
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Quartz
  dependency-version: 3.22.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Quartz.Extensions.DependencyInjection
  dependency-version: 3.22.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Quartz.Extensions.Hosting
  dependency-version: 3.22.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Quartz.Serialization.SystemTextJson
  dependency-version: 3.22.10
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: System.Security.Cryptography.Pkcs
  dependency-version: 10.0.15
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: WolverineFx
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
- dependency-name: WolverineFx.RabbitMQ
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-dependencies
...

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 11, 2026
@github-actions github-actions Bot added the tier:B ADR-0014 Tier B: API, templates, deps, migrations; auto-merges once verified label Nov 11, 2026
@omercelikdev

Copy link
Copy Markdown
Collaborator

Verifier verdict — Dependabot (run 2026-11-11)

Head: db2e64e9b27de302d4307c9ba3c4cbd9b10bc047, on main@02128c5. Result: changes requested. The bump breaks the build and the Oracle provider.

(1) Classification. Every bump is minor or patch:

  • Microsoft.Extensions.* / AspNetCore.TestHost / EF Sqlite / System.Security.Cryptography.Pkcs: 10.0.14 → 10.0.15
  • Microsoft.NET.Test.Sdk: 18.11.0 → 18.11.1
  • WolverineFx, WolverineFx.RabbitMQ: 6.53.0 → 6.64.0
  • OpenTelemetry.Instrumentation.AspNetCore/Http: 1.20.1 → 1.20.2
  • Quartz (4 packages): 3.22.9 → 3.22.10
  • Oracle.ManagedDataAccess.Core: 23.26.301 → 23.26.400
  • Oracle.EntityFrameworkCore: 10.23.26301 → 10.23.26400
  • dotnet-stryker: 5.0.0 → 5.1.0

(2) Scope. ✓ The PR changes only Directory.Packages.props, .config/dotnet-tools.json, and one VersionOverride in Goldpath.Approvals.csproj (Microsoft.Extensions.Hosting 10.0.15).

(3) Licence. The licences are unchanged. The two Oracle ids are still on Oracle's Free Use Terms, which license-gate.py lists by id. But several documents name the exact old pins, so this bump would leave them untrue:

  • ga-gate-status G7, which states "pinned … 10.23.26301 / 23.26.301"
  • the CHANGELOG / O-4 entry: "raises ODP.NET to the repository's 23.26.301 pin"
  • the vendored Quartz tables_oracle.sql, "v3.22.9"

(4) Reproduce: failing. CI's own logs already show it, so I did not spend sandbox time rebuilding it.

  1. The build fails, in every job that restores (gates, integration, every gm / * shape). The error is error NU1109: Detected package downgrade: JasperFx from 2.102.0 to centrally defined 2.95.1, and the same for JasperFx.Events. The cause: WolverineFx 6.64.0 requires JasperFx (>= 2.102.0), but Directory.Packages.props still pins 2.95.1, and Dependabot did not move it.
  2. The Oracle provider regresses (oracle lane). ArchivalOracleTests (2 tests), BulkOracleTests (2) and CampaignCeilingOracleProof fail. The cause is System.ArgumentOutOfRangeException thrown at Oracle.ManagedDataAccess.Client.OracleParameter.set_Size, called from OracleModificationCommandBatch.PrepareArrayBindParameter and BuildInsertWithReturningGroup. The bumped Oracle EF provider/ODP.NET pair breaks EF's batched inserts on Oracle. main fails none of these tests: its only Oracle failure is Campaign Oracle lane: the live-throttle test hangs about half the time since #529 + #558 #571's CampaignOracleTests. The Bulk failures are WaitForStateAsync timeouts downstream of the same insert failure.

(5) CI. Red: gates, integration, oracle, 11 gm / * shapes, and golden manifests (PR subset).

Expected, for the owner. Nobody pushes to this branch.

  • Raise JasperFx and JasperFx.Events to at least 2.102.0 together with WolverineFx 6.64.0.
  • Keep the Oracle pair at 23.26.301 / 10.23.26301 until the set_Size regression is understood. A Dependabot ignore for Oracle.* 23.26.400 is one option.
  • Splitting the Oracle pair out of the group would let the other 16 updates move.

Generated by Claude Code

@omercelikdev omercelikdev added the changes-requested Verifier found problems; the worker fixes these first label Nov 11, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 11, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #572.

@dependabot dependabot Bot closed this Nov 11, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/dot-config/nuget-dependencies-f5afaf4046 branch November 11, 2026 12:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment