Skip to content

Bump WolverineFx and WolverineFx.RuntimeCompilation - #2734

Closed
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/multi-92f382533a
Closed

Bump WolverineFx and WolverineFx.RuntimeCompilation#2734
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/nuget/multi-92f382533a

Conversation

@dependabot

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

Copy link
Copy Markdown
Contributor

Updated WolverineFx from 6.63.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

Commits viewable in compare view.

Updated WolverineFx.RuntimeCompilation from 6.61.0 to 6.64.0.

Release notes

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

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot
Bump WolverineFx and WolverineFx.RuntimeCompilation
37e2701 
Bumps WolverineFx from 6.63.0 to 6.64.0
Bumps WolverineFx.RuntimeCompilation from 6.61.0 to 6.64.0

---
updated-dependencies:
- dependency-name: WolverineFx
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: WolverineFx.RuntimeCompilation
  dependency-version: 6.64.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

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
@coderabbitai

coderabbitai Bot commented Nov 10, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@erwan-joly Claude

erwan-joly commented Nov 10, 2026

Copy link
Copy Markdown
Collaborator

·@·d·ependabot r·ebase

Generated by Claude Code

@dependabot @github

dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown
Contributor Author

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

@dependabot dependabot Bot closed this Nov 10, 2026
@dependabot
dependabot Bot deleted the dependabot/nuget/multi-92f382533a branch November 10, 2026 04:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@erwan-joly