Skip to content

fix: Bump Scalar.AspNetCore and 6 others - #28

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/templates/cloudground/nuget-039018933e
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/templates/cloudground/nuget-039018933e

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updated Scalar.AspNetCore from 2.18.6 to 2.19.0.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned StackExchange.Redis at 3.4.31.

Release notes

Sourced from StackExchange.Redis's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated StackExchange.Redis from 3.4.20 to 3.4.31.

Release notes

Sourced from StackExchange.Redis's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned WolverineFx at 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: JasperFx/wolverine@V6.60.0...V6.61.0

6.60.0

What's Changed

Full Changelog: JasperFx/wolverine@V6.59.1...V6.60.0

6.59.1

This is a patch release with two fixes. Upgrading is a package bump only: there is no schema change and no API change.

SQL Server: the inbox and outbox seek on their indexes again

  • GH-5292 (#​5294): Several of the SQL Server message store's per-envelope statements were scanning the whole envelope table. That cost grows with the size of the inbox and outbox, and those statements run once per message. The cause was how two kinds of value were bound as parameters.
    • Envelope ids went out as sql_variant. The statements that mark envelopes as handled, reassign them, delete them and move them to the dead letter queue all filter on the envelope id. Weasel's generic command builder has no mapping for Guid, so it bound each id as DbType.Object, which SqlClient sends as sql_variant. SQL Server then had to compare CONVERT_IMPLICIT(sql_variant, [id]) on every row, which rules out a seek on the uniqueidentifier primary key. Ids are now bound as uniqueidentifier, so each statement is a primary key seek.
    • Envelope addresses went out as nvarchar. received_at on the inbox and destination on the outbox are varchar(250) columns, but statements that filter on them bound the address as nvarchar. Under a SQL collation such as SQL_Latin1_General_CP1_CI_AS, the default on Azure SQL, that converts the column and defeats the index. The statements affected are the per-envelope updates and deletes, inbox recovery's page load, outbox loads by destination, the scheduled message updates and the duplicate check. They now bind the address as varchar.
    • DateTime parameters kept only the date. The same generic mapping typed DateTime as DbType.Date. The message store now lets SqlClient type both values itself.
    • The new test checks SQL Server's plan cache after running each of these statements. It requires that no plan contains sql_variant and that no plan converts an indexed envelope column. The full SqlServerTests suite passes (721 tests, 2 skipped).
    • PostgreSQL, MySQL, SQLite and Oracle bind exactly as they did before.
    • The underlying Weasel mappings are tracked as JasperFx/weasel#​758 (Guid as sql_variant) and JasperFx/weasel#​759 (DateTime as date). Wolverine works around both on its own, so this release doesn't wait for a Weasel release.

The run command no longer blocks a thread pool thread

  • JasperFx 2.96.2 (JasperFx/jasperfx#​1093, fixes JasperFx/jasperfx#​1092): Wolverine now depends on JasperFx 2.96.2. Before this release, the run command waited for shutdown by blocking a thread pool thread for the whole life of the application. That matters when a container's CPU limit is below one core. ProcessorCount is then 1, so the thread pool's minimum is one thread, and the run command held it. After that, every burst of work had to wait for the pool to add a thread, about 500 ms each time. The reporter saw a 200 ms Task.Delay loop wake up as much as about 950 ms late on Azure Container Apps.
    • The run command now awaits shutdown instead of blocking. It still listens for the same three signals: ApplicationStopping, Ctrl+C, and the assembly load context unloading.
    • When the host is already started (the AutoStartHost / WebApplicationFactory path), RunJasperFxCommands() used to block the calling thread. It now returns a task that completes when the host shuts down.
    • This applies to every application started with RunJasperFxCommands() or RunWolverineCommands(), whatever its persistence or transport.

Full Changelog: JasperFx/wolverine@V6.59.0...V6.59.1

Commits viewable in compare view.

Updated WolverineFx.EntityFrameworkCore from 6.59.0 to 6.64.0.

Release notes

Sourced from WolverineFx.EntityFrameworkCore'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: JasperFx/wolverine@V6.60.0...V6.61.0

6.60.0

What's Changed

Full Changelog: JasperFx/wolverine@V6.59.1...V6.60.0

6.59.1

This is a patch release with two fixes. Upgrading is a package bump only: there is no schema change and no API change.

SQL Server: the inbox and outbox seek on their indexes again

  • GH-5292 (#​5294): Several of the SQL Server message store's per-envelope statements were scanning the whole envelope table. That cost grows with the size of the inbox and outbox, and those statements run once per message. The cause was how two kinds of value were bound as parameters.
    • Envelope ids went out as sql_variant. The statements that mark envelopes as handled, reassign them, delete them and move them to the dead letter queue all filter on the envelope id. Weasel's generic command builder has no mapping for Guid, so it bound each id as DbType.Object, which SqlClient sends as sql_variant. SQL Server then had to compare CONVERT_IMPLICIT(sql_variant, [id]) on every row, which rules out a seek on the uniqueidentifier primary key. Ids are now bound as uniqueidentifier, so each statement is a primary key seek.
    • Envelope addresses went out as nvarchar. received_at on the inbox and destination on the outbox are varchar(250) columns, but statements that filter on them bound the address as nvarchar. Under a SQL collation such as SQL_Latin1_General_CP1_CI_AS, the default on Azure SQL, that converts the column and defeats the index. The statements affected are the per-envelope updates and deletes, inbox recovery's page load, outbox loads by destination, the scheduled message updates and the duplicate check. They now bind the address as varchar.
    • DateTime parameters kept only the date. The same generic mapping typed DateTime as DbType.Date. The message store now lets SqlClient type both values itself.
    • The new test checks SQL Server's plan cache after running each of these statements. It requires that no plan contains sql_variant and that no plan converts an indexed envelope column. The full SqlServerTests suite passes (721 tests, 2 skipped).
    • PostgreSQL, MySQL, SQLite and Oracle bind exactly as they did before.
    • The underlying Weasel mappings are tracked as JasperFx/weasel#​758 (Guid as sql_variant) and JasperFx/weasel#​759 (DateTime as date). Wolverine works around both on its own, so this release doesn't wait for a Weasel release.

The run command no longer blocks a thread pool thread

  • JasperFx 2.96.2 (JasperFx/jasperfx#​1093, fixes JasperFx/jasperfx#​1092): Wolverine now depends on JasperFx 2.96.2. Before this release, the run command waited for shutdown by blocking a thread pool thread for the whole life of the application. That matters when a container's CPU limit is below one core. ProcessorCount is then 1, so the thread pool's minimum is one thread, and the run command held it. After that, every burst of work had to wait for the pool to add a thread, about 500 ms each time. The reporter saw a 200 ms Task.Delay loop wake up as much as about 950 ms late on Azure Container Apps.
    • The run command now awaits shutdown instead of blocking. It still listens for the same three signals: ApplicationStopping, Ctrl+C, and the assembly load context unloading.
    • When the host is already started (the AutoStartHost / WebApplicationFactory path), RunJasperFxCommands() used to block the calling thread. It now returns a task that completes when the host shuts down.
    • This applies to every application started with RunJasperFxCommands() or RunWolverineCommands(), whatever its persistence or transport.

Full Changelog: JasperFx/wolverine@V6.59.0...V6.59.1

Commits viewable in compare view.

Updated WolverineFx.Postgresql from 6.59.0 to 6.64.0.

Release notes

Sourced from WolverineFx.Postgresql'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

Description has been truncated

Bumps Scalar.AspNetCore from 2.18.6 to 2.19.0
Bumps StackExchange.Redis to 3.4.31
Bumps WolverineFx from 6.59.0 to 6.64.0
Bumps WolverineFx.EntityFrameworkCore from 6.59.0 to 6.64.0
Bumps WolverineFx.Postgresql from 6.59.0 to 6.64.0
Bumps WolverineFx.RabbitMQ from 6.59.0 to 6.64.0
Bumps WolverineFx.RuntimeCompilation from 6.59.0 to 6.64.0

---
updated-dependencies:
- dependency-name: Scalar.AspNetCore
  dependency-version: 2.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: StackExchange.Redis
  dependency-version: 3.4.31
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
- dependency-name: StackExchange.Redis
  dependency-version: 3.4.31
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: nuget
- dependency-name: StackExchange.Redis
  dependency-version: 3.4.31
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget
- dependency-name: WolverineFx
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: WolverineFx.EntityFrameworkCore
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: WolverineFx.Postgresql
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: WolverineFx.RabbitMQ
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
- dependency-name: WolverineFx.RuntimeCompilation
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget
...

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 10, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 17, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 17, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/templates/cloudground/nuget-039018933e branch November 17, 2026 14:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants