Skip to content

Bump dotnet-stryker and 18 others - #572

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

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

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.

Pinned Microsoft.Extensions.Configuration.Binder at 9.0.23.

Release notes

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

9.0.23

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.21...v9.0.23

9.0.22

Release

Full Changelog: dotnet/runtime@v9.0.21...v9.0.22

9.0.21

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.20...v9.0.21

9.0.20

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.19...v9.0.20

9.0.19

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.18...v9.0.19

9.0.18

Release

What's Changed

Full Changelog: dotnet/runtime@v9.0.17...v9.0.18

Commits viewable in compare view.

Pinned Microsoft.Extensions.Configuration.Binder at 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.

Pinned Microsoft.Extensions.Hosting at 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.

Pinned Microsoft.Extensions.Hosting at 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.Extensions.Hosting.Abstractions from 10.0.14 to 10.0.15.

Release notes

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

No release notes found for this version range.

Commits viewable in compare view.

Updated Microsoft.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.

Pinned Quartz at 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.

Pinned Quartz.Extensions.DependencyInjection at 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.

Pinned Quartz.Extensions.Hosting at 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.

Pinned Quartz.Serialization.SystemTextJson at 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 sto...

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 to 9.0.23, 10.0.15
Bumps Microsoft.Extensions.Hosting to 10.0.15
Bumps Microsoft.Extensions.Hosting.Abstractions 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.Configuration.Binder
  dependency-version: 9.0.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.Extensions.Configuration.Binder
  dependency-version: 9.0.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-dependencies
- dependency-name: Microsoft.Extensions.Configuration.Binder
  dependency-version: 9.0.23
  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.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.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.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.Abstractions
  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.Extensions.Hosting
  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.Extensions.Hosting
  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-12)

Head: d6070f66e7f064b538da1844c89362f847ceb549 · Verdict: FINDINGS — changes-requested (the build is red, and the diff goes beyond version bumps)

1. Classification — no majors

The body is truncated, so the 19 bumps were read from the diff. All are minor or patch:

  • dotnet-stryker 5.0.0→5.1.0 (minor)
  • Microsoft.AspNetCore.TestHost, Microsoft.Extensions.Configuration.Binder, Microsoft.Extensions.Hosting, Microsoft.Extensions.Hosting.Abstractions, Microsoft.Extensions.Caching.StackExchangeRedis, Microsoft.EntityFrameworkCore.Sqlite, System.Security.Cryptography.Pkcs: 10.0.14→10.0.15 (patch)
  • Microsoft.NET.Test.Sdk 18.11.0→18.11.1 (patch)
  • WolverineFx, WolverineFx.RabbitMQ 6.53.0→6.64.0 (minor)
  • OpenTelemetry.Instrumentation.AspNetCore / .Http 1.20.1→1.20.2 (patch)
  • Quartz, Quartz.Extensions.DependencyInjection, Quartz.Extensions.Hosting, Quartz.Serialization.SystemTextJson 3.22.9→3.22.10 (patch)
  • Oracle.ManagedDataAccess.Core 23.26.301→23.26.400 and Oracle.EntityFrameworkCore 10.23.26301→10.23.26400 (minor)

2. Scope — FINDING

  • Two finding — new package references, not version bumps. 11 .csproj files gain a PackageReference they did not have before:
    • Shipped packages: Goldpath.Approvals, Goldpath.Campaign and Goldpath.FileExchange gain Microsoft.Extensions.Hosting VersionOverride="10.0.15". Goldpath.AuditTrail, Goldpath.Auth and Goldpath.Idempotency gain Microsoft.Extensions.Configuration.Binder VersionOverride="9.0.23".
    • Tests: AuditTrail.Tests, Bulk.Tests, Data.Tests and SoftDelete.Tests gain Configuration.Binder. Messaging.Conformance gains Hosting.
    • These change the dependency graph of six published nupkgs. The VersionOverrides also bypass central pinning. A dependency PR may not do either.
  • Incomplete family bump. WolverineFx.Newtonsoft stays at 6.53.0, and JasperFx, JasperFx.Events and JasperFx.SourceGenerator stay at 2.95.1. Wolverine 6.64.0 needs JasperFx >= 2.102.0 and WolverineFx.Newtonsoft >= 6.64.0, and Goldpath.Messaging.Wolverine pins its transitive packages exactly (CentralPackageTransitivePinningEnabled, G5 Part 1/5: the Wolverine adapter, the eight conformance facts green on both engines #330). The result is the build break in step 4.
  • Stale comment (minor). The Oracle block in Directory.Packages.props still says the pin is .26301 / 23.26.301 and that .26400 "is eligible from 2026-11-03". The pin is now .26400, so the comment should be updated with it.
  • Gates — all green:
    • template-pins.sh exit 0 ("templates and the adopter docs are all on the train")
    • docs-freshness.sh exit 0
    • ledger-check.sh exit 0 (no authenticated gh, so it skipped the online half)
    • schema-honesty.sh exit 0
    • skills-parity.sh exit 0
  • Note (not counted as a finding): templates/goldpath-{solution,worker}/Directory.Packages.props still pin System.Security.Cryptography.Pkcs 10.0.14 (the advisory lift) while the root moves to 10.0.15. template-pins.sh does not cover that pin. No template pin conflicts with this PR.

3. Security and licence

  • Licences unchanged (read from the restored nuspecs at the new versions):
    • Microsoft.* and WolverineFx: MIT
    • OpenTelemetry and Quartz: Apache-2.0
    • dotnet-stryker 5.1.0: Apache-2.0 (LICENSE file)
    • Oracle 23.26.400 / 10.23.26400: LICENSE.txt is byte-identical to the previous pins (Oracle FUTC, inside the existing scoped exception)
  • Vulnerability scan could not run. dotnet list Goldpath.sln package --vulnerable --include-transitive exits 1 on the NU1109 restore failure, so no clean result can be stated until restore succeeds.

4. Reproduce — FINDING

dotnet build Goldpath.sln -c Release fails with exit 1 and 4 NU1109 errors (24 diagnostic lines), all in packages/Goldpath.Messaging.Wolverine:

error NU1109: Detected package downgrade: JasperFx from 2.102.0 to centrally defined 2.95.1.
  Goldpath.Messaging.Wolverine -> WolverineFx 6.64.0 -> JasperFx (>= 2.102.0)
error NU1109: ... JasperFx.Events from 2.102.0 to centrally defined 2.95.1.
error NU1109: ... JasperFx.SourceGenerator from 2.102.0 to centrally defined 2.95.1.
error NU1109: Detected package downgrade: WolverineFx.Newtonsoft from 6.64.0 to centrally defined 6.53.0.
  Goldpath.Messaging.Wolverine -> WolverineFx.RabbitMQ 6.64.0 -> WolverineFx.Newtonsoft (>= 6.64.0)

The affected tests (Goldpath.Messaging.Conformance and the solution's test projects) cannot run, because restore fails first.

dotnet-stryker 5.1.0 restores (dotnet tool restore OK) and --help exits 0. All 23 configs in stryker/*.json parse as JSON. No dry run was done, because the solution does not restore.

5. CI on the head

  • Green: merge-policy, kit, review, gm-scope, gm / plan, CodeQL (csharp, js-ts), tier-label
  • Red: gates, integration, golden manifests (PR subset) and all 11 gm / Gm* shapes. Each fails on the same NU1109 errors, and all of them are green on main c9d23ae (gates, integration and the GM PR subset all succeed there). ADR-0008 means no merge while GM is red.
  • Red, not counted: oracle (required: no; also red on main).

What fixes it:

  • Move WolverineFx.Newtonsoft to 6.64.0 and the three JasperFx* packages to 2.102.0 in the same PR. Check that the rest of the pinned Wolverine family still resolves, then rerun the messaging conformance suite.
  • Remove the 11 added PackageReference/VersionOverride lines.
  • Update the Oracle pin comment.

One way to do this is to split Wolverine into its own PR and land the 17 patch-level bumps on their own.


Generated by Claude Code

@omercelikdev omercelikdev added the changes-requested Verifier found problems; the worker fixes these first label Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment