Repository navigation
Bump dotnet-stryker and 18 others - #572
dependabot[bot] wants to merge 1 commit into
Conversation
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>
Verifier verdict — Dependabot (run 2026-11-12)Head: 1. Classification — no majorsThe body is truncated, so the 19 bumps were read from the diff. All are minor or patch:
2. Scope — FINDING
3. Security and licence
4. Reproduce — FINDING
The affected tests (
5. CI on the head
What fixes it:
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 |
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
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
NuGet: OpenTelemetry.Extensions.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.2
server.addressandserver.portnot being recorded correctly for HTTPrequests with an IPv6 address in the
Hostheader (e.g.[::1]:8080).(#5788)
See CHANGELOG for details.
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
RecordExceptionis enabled.(#5884)
Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
(#5886)
Added
EnrichWithBackgroundJobandCustomStateMappingstoHangfireMetricsInstrumentationOptions. Use them to add custom attributes tothe metrics and to count jobs in custom Hangfire states.
(#5810)
Fixed
workflow.execution.durationfor theexecutingstate. It included thetime of other measurements of this instrumentation, for example the database
query that
RecordQueueLatencyadds.(#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
NuGet: OpenTelemetry.Extensions.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.2
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.2
server.addressandserver.portnot being recorded correctly for HTTPrequests with an IPv6 address in the
Hostheader (e.g.[::1]:8080).(#5788)
See CHANGELOG for details.
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
RecordExceptionis enabled.(#5884)
Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
(#5886)
Added
EnrichWithBackgroundJobandCustomStateMappingstoHangfireMetricsInstrumentationOptions. Use them to add custom attributes tothe metrics and to count jobs in custom Hangfire states.
(#5810)
Fixed
workflow.execution.durationfor theexecutingstate. It included thetime of other measurements of this instrumentation, for example the database
query that
RecordQueueLatencyadds.(#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
Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @EnesKartal. (#4190, closes #4188)CronTriggerImplclone has a job data map of its own. It usedMemberwiseClonerather than the base clone that every other trigger type uses, so the clone shared the original'sJobDataMap.RAMJobStorestores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#4205)FailedJobOriginalTrigger*markers.IJobExecutionContext.RecoveringTriggerKeythen 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)doubleto thedecimalnearest its exact binary value. So when a driver returns theDEC_PROP_1/2columns as adouble, as SQLite's does,12.34came back as12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4219, from #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring that .NET splits on whitespace, so the parameters never reached the command. (#4220, from #4212)NativeJobkills the process tree, and the job ends as cancelled rather than withError launching native command. (#4220)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4220)<base href>sent it under the dashboard path, where onlyblazor.web.jsandopaque-redirectwere mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole_frameworktree under its path. Thanks to the Marten Studio maintainers for the report. (#4227, from #4224)ObjectDisposedExceptionwhen 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 logsError managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412. (#4261, from #4255)Packaging
Quartz.Jobsgains anet8.0build, which .NET 8 and later now pick up instead ofnetstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. Thenetstandard2.0and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the otherNativeJobchanges.Compatibility
On Linux with .NET 8 or later, a
NativeJobcommand that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments toparameters.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
Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @EnesKartal. (#4190, closes #4188)CronTriggerImplclone has a job data map of its own. It usedMemberwiseClonerather than the base clone that every other trigger type uses, so the clone shared the original'sJobDataMap.RAMJobStorestores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#4205)FailedJobOriginalTrigger*markers.IJobExecutionContext.RecoveringTriggerKeythen 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)doubleto thedecimalnearest its exact binary value. So when a driver returns theDEC_PROP_1/2columns as adouble, as SQLite's does,12.34came back as12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4219, from #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring that .NET splits on whitespace, so the parameters never reached the command. (#4220, from #4212)NativeJobkills the process tree, and the job ends as cancelled rather than withError launching native command. (#4220)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4220)<base href>sent it under the dashboard path, where onlyblazor.web.jsandopaque-redirectwere mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole_frameworktree under its path. Thanks to the Marten Studio maintainers for the report. (#4227, from #4224)ObjectDisposedExceptionwhen 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 logsError managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412. (#4261, from #4255)Packaging
Quartz.Jobsgains anet8.0build, which .NET 8 and later now pick up instead ofnetstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. Thenetstandard2.0and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the otherNativeJobchanges.Compatibility
On Linux with .NET 8 or later, a
NativeJobcommand that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments toparameters.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
Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @EnesKartal. (#4190, closes #4188)CronTriggerImplclone has a job data map of its own. It usedMemberwiseClonerather than the base clone that every other trigger type uses, so the clone shared the original'sJobDataMap.RAMJobStorestores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#4205)FailedJobOriginalTrigger*markers.IJobExecutionContext.RecoveringTriggerKeythen 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)doubleto thedecimalnearest its exact binary value. So when a driver returns theDEC_PROP_1/2columns as adouble, as SQLite's does,12.34came back as12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4219, from #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring that .NET splits on whitespace, so the parameters never reached the command. (#4220, from #4212)NativeJobkills the process tree, and the job ends as cancelled rather than withError launching native command. (#4220)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4220)<base href>sent it under the dashboard path, where onlyblazor.web.jsandopaque-redirectwere mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole_frameworktree under its path. Thanks to the Marten Studio maintainers for the report. (#4227, from #4224)ObjectDisposedExceptionwhen 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 logsError managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412. (#4261, from #4255)Packaging
Quartz.Jobsgains anet8.0build, which .NET 8 and later now pick up instead ofnetstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. Thenetstandard2.0and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the otherNativeJobchanges.Compatibility
On Linux with .NET 8 or later, a
NativeJobcommand that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments toparameters.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
Invalid cron expression: …, the reason the preview already gave, and leaves the page and the trigger as they were. Thanks @EnesKartal. (#4190, closes #4188)CronTriggerImplclone has a job data map of its own. It usedMemberwiseClonerather than the base clone that every other trigger type uses, so the clone shared the original'sJobDataMap.RAMJobStorestores and hands out clones, so a write to a retrieved cron trigger's map reached the stored trigger. (#4205)FailedJobOriginalTrigger*markers.IJobExecutionContext.RecoveringTriggerKeythen 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)doubleto thedecimalnearest its exact binary value. So when a driver returns theDEC_PROP_1/2columns as adouble, as SQLite's does,12.34came back as12.339999999999999857891452848. Quartz now rounds to 15 (double) or 7 (float) significant digits, as every earlier runtime did. (#4219, from #4210)NativeJobpasses its parameters to the shell on Linux. The command and its parameters were joined into oneArgumentsstring that .NET splits on whitespace, so the parameters never reached the command. (#4220, from #4212)NativeJobkills the process tree, and the job ends as cancelled rather than withError launching native command. (#4220)NativeJobreads 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)NativeJobruns the system directory'scmd.exeon Windows, never one thatPATHor the working directory finds first. (#4220)<base href>sent it under the dashboard path, where onlyblazor.web.jsandopaque-redirectwere mirrored. So it failed, and the Blazor circuit never started. The dashboard now serves the whole_frameworktree under its path. Thanks to the Marten Studio maintainers for the report. (#4227, from #4224)ObjectDisposedExceptionwhen 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 logsError managing cluster: NpgsqlTransaction. Thanks @mrreddevil2412. (#4261, from #4255)Packaging
Quartz.Jobsgains anet8.0build, which .NET 8 and later now pick up instead ofnetstandard2.0. The Linux parameter fix and the process-tree kill need APIs only that build has. Thenetstandard2.0and .NET Framework builds keep their old Linux command line, and leave a cancelled job's process running as before. They do get the otherNativeJobchanges.Compatibility
On Linux with .NET 8 or later, a
NativeJobcommand that wrapped itself in quotes to work around the old whitespace split now passes those quotes to the shell. Remove the quotes, or move the arguments toparameters.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
NativeAckendpoint, 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).IWolverineObserver.CircuitBreakerResetis now raised, once per trip, when a listener the breaker paused accepts messages again. Nothing ever raised it before, so an alert opened onCircuitBreakerTrippedcould never be closed by Wolverine's own signal. A new overload,CircuitBreakerReset(Endpoint, CircuitBreakerResetReason), says whether the listener came back on its own afterPauseTimeor through an explicit start or restart. Its default forwards to the existing one-argument member, so existing observers keep working unchanged (GH-5446).ResetResourceState()no longer adds a newwolverine.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, soInvokeAsync<T>()timed out (GH-5452, thanks to @alesdvorakcz).Docs
AutoCreate(#5445).What's Changed
ResetResourceState()calls by @alesdvorakcz in GH-5452: Rabbit MQ keeps one reply queue acrossResetResourceState()calls JasperFx/wolverine#5453Full 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