Bump WolverineFx from 6.19.0 to 6.23.0

[dependabot]

Updated WolverineFx from 6.19.0 to 6.23.0.

Release notes

Sourced from WolverineFx's releases.

6.23.0

Projection & agent distribution

TL;DR: this prevents Wolverine from going into a panic doing agent assignments and churning crazily hard during Kubernetes rollouts or cluster starts and that's a very good thing

The bulk of this release. A wave of fixes (WO-1..8) to the agent assignment plane that together remove the re-assignment churn and livelock that could leave projection agents flapping or wedged.

• Node heartbeats no longer block behind command execution (#​3620)
• Node resurrection restores the node's real identity rather than a skeleton record (#​3621)
• A pending-assignment ledger suppresses duplicate AssignAgent floods (#​3622)
• Agent batch starts are chunked and bounded-parallel, so they stay safe at scale (#​3623)
• Ejection hysteresis plus leader protection (#​3624)
• The assignment row is re-upserted for agents that are already running (#​3619)
• Local agents drain with bounded parallelism on shutdown (#​3636)
• Paused shards now say why. IEventSubscriptionAgent.Failure surfaces a ShardFailure — category, the failing event's sequence and type, and the root exception type — through health checks and a new IWolverineObserver.AgentPaused hook plus a NodeRecordType.AgentPaused record. Failures bound to a specific event (ApplyEvent, EventSerialization, UnknownEventType) or to two processes racing one shard (ProgressionOutOfOrder) are no longer auto-restarted, since they would die on the identical event every time (#​3637, #​3638)
• Agent starts retry locally, bounded by Durability.AgentStartRetryAttempts / AgentStartRetryDelay, instead of idling a full CheckAssignmentPeriod after a startup race (#​3519)
• Store-scoped FindAgentUriAsync overload (#​3647) and a store-aware TryRebuildRegisteredProjectionAsync overload (#​3618)

Bumps JasperFx.Events to 2.36.1, Marten to 9.20.0 and Polecat to 5.7.0.

HTTP

• Endpoints that advertise a request body their HTTP method cannot carry now fail fast at startup instead of silently 404ing out of the route matcher (#​3648)
• A missing Content-Type on an [AcceptsContentType] route returns 415 rather than 404 (#​3649)
• Query-only [AsParameters] endpoints no longer advertise a form body, which had been dropping them from route matching entirely (#​3630)
• Explicitly-routed chains — PublishMessage<T> and SendMessage<T> — now describe the message they read from the body. They had been advertising no request body at all in OpenAPI (#​3646)
• Enum values in query strings and form posts parse case-insensitively (#​3629)
• Compiled queries returned as a Wolverine.Http resource no longer execute twice (#​3625)

Transports

• Conventional routing respects named brokers (#​3633)
• Google Pub/Sub: named-broker support for sharded and partitioned topics (#​3632), and ListenToPubsubSubscriptionOnNamedBroker (#​3631)
• Kafka: topic-already-exists error codes are handled rather than thrown (#​3640)
• Redis: scheduled retries survive an unreadable timestamp (#​3613), and scheduled entries that repeatedly fail to deserialize are dead-lettered instead of looping (#​3644)
• EnvelopeMapper reads both timestamp header formats (#​3645)
• NServiceBus interop: the EnclosedMessageTypes header is split before the message type is resolved, so interop works across Azure Service Bus, SNS, SQS and the database transports (#​3628)

Persistence

• Oracle runs the durability agent through the shared batching mechanics (#​3614). Note that ODP.NET exposes no DbBatch, so the work splits per statement.

Other

• Resource discovery no longer eager-connects broker transports (#​3617)

Contributors

Thank you to everyone who contributed to this release:

... (truncated)

6.22.0

Wolverine 6.22.0 rolls up the claim-check backend wave, distributed-agent and durability hardening, HTTP/OpenAPI binding fixes, and the Marten 9.18 / JasperFx 2.34 critter-stack alignment.

Dependency alignment

• JasperFx family → 2.34.0
• Marten → 9.18.0 (with Marten.AspNetCore / Marten.Newtonsoft), Polecat [5.5.0,6.0.0)
• Weasel family → 9.18.1

Claim-check offloading

• New NATS JetStream Object Store claim-check backend (#​3506)
• New PostgreSQL database-LOB claim-check backend (#​3507)
• New Google Cloud Storage claim-check backend (#​3505)
• Size-threshold auto-offload — large payloads offload to the claim-check store automatically (#​3504)
• Per-message / per-endpoint store selection (#​3508)
• Honor a DI-registered IClaimCheckStore (#​3564)
• New claim-check backends are now packed for NuGet (#​3565)

Distributed agents & durability

• Recover exclusive listener inboxes on the listening node (#​3590)
• Reverse the reset-clears-queue-tables behavior; add IHost.ClearAllWolverineStorageAsync() (#​3592)
• Subscription health check uses the tenant-scoped high water mark for per-tenant subscription agents (#​3582)
• Isolate agent start failures so one wedged agent no longer skips its siblings (#​3519)
• Restart a projection agent whose shard wedged out from under it (#​3519)
• EventSubscriptionAgent restores continuous execution after Rebuild/Rewind (#​3520)
• Stamp the assigned node onto owned event-store daemons (running_on_node, marten#​5001) (#​3578)
• Solo-mode health-check loop no longer leaks an unbounded OpenTelemetry trace (#​3518)
• Warn loudly when a host's application assembly is pinned by an earlier host (#​3521)

HTTP & OpenAPI

• Describe chain-bound OpenAPI params from produced variables; narrow re-reflection to postprocessors (#​3601)
• Bind [FromQuery] on arrays/collections instead of misrouting to complex-flattening (#​3602)
• Bind scalar [FromQuery] decimal correctly + shape-test OpenAPI parameter description across type families (#​3586)
• Don't describe a route-bound [FromQuery]/[FromHeader] parameter twice in OpenAPI (#​3586)
• Marten 9.18 streaming types — StreamPaged, StreamPagedByCursor, ETag support (#​3593)
• Honour opt-in discovery filters for HTTP endpoint discovery (#​3525)
• Never infer a DbContext parameter as the HTTP request body (#​3538)

Transports

• Add a parallel WolverineFx.Mqtt5 package (MQTTnet 5) (#​3517)
• Pulsar: don't claim native scheduling without a retry-letter topic (#​3491)
• Azure Service Bus: pin session listeners to specific session identifiers (#​3533)

Persistence

• Clear transport queue tables on message-store reset — PostgreSQL (#​3529), SQLite (#​3553), MySQL (#​3551), Oracle (#​3552)
• Oracle: durable inbox mark-as-handled binds RAW(16) Guid correctly (#​3581)
  ... (truncated)

6.21.0

Wolverine 6.21.0 is a big one: conjoined multi-tenancy for EF Core, and a measured messaging-performance wave across Kafka and RabbitMQ.

Conjoined multi-tenancy for EF Core (#​3465)

Mark an EF Core entity with ITenanted (the marker shared critter-stack-wide from JasperFx.MultiTenancy) and register your DbContext with AddDbContextWithWolverineManagedConjoinedTenancy<T>(), and Wolverine gives you what Marten users have had for years: a mapped tenant_id column, a tenant-bound global query filter you can't forget, stamp-on-insert, CrossTenantWriteException on cross-tenant writes, conjoined sagas, opt-in Weasel-managed physical tenant partitioning (PostgreSQL list partitions + SQL Server tenant-ordinal), and an authoritative wolverine_tenants registry that doubles as a dynamic tenant source and feeds CritterWatch tenant management. The behavior is checked against a port of Marten's conjoined-tenancy compliance battery. See the new ConjoinedMultiTenantedEfCore sample app and docs.

Messaging performance (GH-3490 / GH-3492)

A client-reported "Wolverine-over-Kafka is 3-12x slower than native" investigation turned into a measured optimization wave (methodology, rigs, and full ledgers are in the repo):

• Sender batching now flushes within the batch timeout (JasperFx 2.30.1). The batch timer was a quiet-period debounce — a steady 8 msg/s stream at the default (100, 250ms) settings measured 5.8 seconds publish-to-consume p50; it now measures 136ms, bounded by the timeout. Affects every transport that sends through the batched sender (RabbitMQ routes were unaffected — they don't).
• Durable (inbox-backed) listeners batch their inbox writes. Kafka: a 2,000 msg/s stream went from unbounded backlog to a steady 32ms delivery p50, max sustained durable throughput +83%. RabbitMQ: same load went from 14.7s-and-climbing to 0.8ms delivery p50, max sustained durable throughput +186% (1,086 → 3,101 msg/s). New MaximumMessagesToReceive listener knob on both (default 100; 1 restores strict message-at-a-time persistence).
• Kafka hot path: incoming envelope mapping ~21% faster / ~28% less allocation per message; outgoing ~17% faster; inline senders no longer issue a blocking full-producer flush per send. RabbitMQ's mapper gets the same incoming fix.
• Batch-arrival correctness: the Envelope[] arrival path now applies the same per-envelope guards as single-message arrival (interop serializer unwrap, dead-lettering of unidentifiable messages, expiry, drain latching), and batched inbox writes route to ancillary message stores correctly.
• SQS: SendMessageBatch per-entry failures (throttling, oversize) are now routed to Wolverine's retry machinery instead of being silently dropped — a silent message-loss fix (GH-3493).
• Out-of-the-box RabbitMQ consumption is Inline — one message at a time, which measures identically to an equivalent single-consumer raw-client loop. The new RabbitMQ "Performance Tuning" docs page covers scaling with BufferedInMemory() / ListenerCount() with measured numbers, and a matching page exists for Kafka.

Behavior changes to note

• The per-message "successfully processed" log now defaults to Debug (was Information) — restore with opts.Policies.MessageSuccessLogLevel(LogLevel.Information).
• wolverine-execution-time is now a floating-point histogram and no longer silently drops sub-millisecond executions (same name/unit; the point type changes).

Transports and messaging

• Azure Service Bus: PrefetchCount on listeners and transport defaults (GH-3471)
• SQS: native DelaySeconds for short scheduled sends on standard queues (GH-3472)
• Pulsar: native scheduled delivery via DeliverAt (GH-3470)
• Kafka: KIP-848 next-generation consumer rebalance protocol support (GH-3473)
• Standardized diagnostic headers on dead-letter and retry moves across all transports (GH-3474)
• SignalR cascading responses are no longer dropped when the HTTP context has already flushed (GH-3499)
• The dead-letter metric only counts genuine moves to the error queue (#​3495)
• Global partitioning docs now cover all eight sharded transports (GH-3466)
• Tolerate empty agent URI lists in agent command serialization (GH-3460)

HTTP / gRPC

• Code-first gRPC client streaming: IAsyncEnumerable<TRequest> -> Task<TResponse> handler shape (#​3500)
• Proto-first gRPC client streaming via the new StreamAsync<TRequest, TResponse> overload (#​3459)

Dependencies

JasperFx 2.30.1 (sender-batching max-age fix), Weasel 9.18.1, Marten 9.16.1.

6.20.0

Wolverine 6.20.0

Dependency upgrades (critter stack)

• Marten 9.16.0, Polecat 5.2.0, JasperFx 2.29.0, Weasel 9.17.0 (aligned across the stack).

Multi-tenancy & connection footprint

• Scope tenant scheduled-job polling to the owning node (GH-3376) — under Wolverine-managed distribution, nodes no longer open a scheduled-job polling connection to every tenant database; the footprint scales with databases, not nodes × databases. Plus daemon tracker-subscription leak hygiene.
• Polecat primary-store database-per-tenant (GH-3445) — IntegrateWithWolverine() now honors a database-per-tenant Polecat store and reads MainDatabaseConnectionString.
• DatabaseServerId sourced from DatabaseDescriptor.Port instead of re-parsing (jasperfx#​514).

CritterWatch / connection state

• Degrade-only connection state for Azure Service Bus, GCP Pub/Sub (GH-3237) and Kafka (GH-3454) listeners — heuristics only degrade to Reconnecting/Disconnected from real SDK callbacks; they never synthesize Connected, and resting state is Unknown.

Kafka

• Read record timestamps into SentAt and expose record headers on raw-JSON listeners (GH-3407).
• JsonSerializerOptions on raw-JSON endpoints now actually applies; PublishRawJson mapper registration fixed.
• Bounded the listener shutdown drain instead of awaiting forever (GH-3434).

Sagas

• SagaConcurrencyException now inherits JasperFx.ConcurrencyException (GH-3444) — existing OnException<ConcurrencyException>() policies now catch saga concurrency failures.
• Lightweight RDBMS saga provider treated as a catch-all so Marten/EF Core win precedence in mixed-storage hosts (GH-3443).

Other

• Ancillary Marten store now registers the event-subscription family interface aliases (GH-3438).
• F# code generation improvements (#​3437); TrackedSession not-tracked vs not-routed fix (#​3435).
• Buffered circuit-breaker tests re-scoped to the transport's non-durable contract (GH-3137); durability docs corrections.

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]

Superseded by #104.