[dependabot]

Updated WolverineFx from 6.51.3 to 6.54.0.

Release notes

Sourced from WolverineFx's releases.

6.54.0

Highlights

Dead letter failure groups (#​5209, #​5210). Wolverine now fingerprints every message as it moves to dead letter storage, so dead letters can be managed one failure group at a time:

• The default IDeadLetterFingerprinter hashes the exception type and the first stack frame from application code. Register your own to replace it.
• DeadLetterEnvelopeQuery gains FailureGroup, ExceptionMessageMatch (Exact / Contains), TenantId and Archived.
• A new SummarizeAllAsync overload groups by failure group, message type or endpoint, with first and last failure times.
• ReplayMatchingAsync, DiscardMatchingAsync, ArchiveMatchingAsync and RestoreMatchingAsync report how many dead letters they affected.
• A message that fails again after a replay reports its ReplayCount, LastReplayedAt and FirstFailedAt.
• Archived dead letters drop out of summaries, queries and replays until restored, and can be expired separately with DurabilitySettings.ArchivedDeadLetterRetention.
• IDeadLetters.Capabilities tells you what a store supports.

All changes are additive. The relational stores pick up seven nullable columns on wolverine_dead_letters, an index and a new wolverine_dead_letter_history table through the normal schema migration. See the dead letter storage guide.

Deduplication fixes (#​5205, #​5206, #​5208), and Bobcat 1.0.0-rc.4 dependency pins (#​5211). The WolverineFx.Bobcat* packages remain alpha (6.54.0-alpha.1).

What's Changed

• GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) by @​jeremydmiller in GH-5205, GH-5206: [DeduplicatedWithResponse] claim-in-transaction gaps ([WriteAggregate] T / [BoundaryModel], and repeats refused over committed work) JasperFx/wolverine#5208
• Bobcat 1.0.0-rc.4 by @​jeremydmiller in Bobcat 1.0.0-rc.4 JasperFx/wolverine#5211
• GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping by @​jeremydmiller in GH-5209 Dead letters: failure fingerprints, operation counts, replay history, archive/restore and tenant scoping JasperFx/wolverine#5210

Full Changelog: JasperFx/wolverine@V6.53.0...V6.54.0

6.53.0

What's Changed

• GH-5202: keep the ASB response queue identity stable during startup by @​DeandreT in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

New Contributors

• @​DeandreT made their first contribution in GH-5202: keep the ASB response queue identity stable during startup JasperFx/wolverine#5203

Full Changelog: JasperFx/wolverine@V6.52.0...V6.53.0

6.52.0

Wolverine 6.52.0 is a feature release. The headline items are Aspire-style registration by connection-string name for every transport and every message store, timer agents for short-cadence recurring schedules, and the 6.x groundwork for Wolverine 7.0's one-chain-per-handler model. There are no breaking API changes. Two behavior changes are worth knowing about up front: recurring schedules that fire more often than every 15 minutes now run on a timer agent (opt out per schedule with UseScheduledMessages()), and outgoing envelopes a transport cannot map are dead-lettered instead of being logged and deleted.

Many thanks to everyone who reported issues and sent fixes: @​uniquelau, @​johnkaram02, @​erdtsieck, @​ahmetvayhan and @​pritamrao.

Aspire parity: named connections

• Named-connection overloads for every transport (Aspire parity, GH-5126) by @​jeremydmiller in Named-connection overloads for every transport (Aspire parity, GH-5126) JasperFx/wolverine#5159
• Message storage by connection-string name for every RDBMS provider (PostgreSQL, SQL Server, MySQL, SQLite, Oracle), NpgsqlDataSource / MySqlDataSource from the container, named static tenants, a Named Connection Strings table in describe, and docs that lead with the named form (GH-5127, GH-5156) by @​jeremydmiller in Message storage by connection-string name for every RDBMS provider, plus named-connection docs and describe (GH-5127, GH-5156) JasperFx/wolverine#5174
• Aspire samples moved to Aspire 13.6.3, added to wolverine.slnx, with a ServiceDefaults project for traces, metrics and /health (GH-5124) by @​jeremydmiller in GH-5124 Aspire samples on Aspire 13.6.3 with shared service defaults, in wolverine.slnx JasperFx/wolverine#5182

Messaging and error handling

• Timer agents for short-cadence recurring schedules: one agent per schedule under opts.Schedules.TimerThreshold (15 minutes), same dedup id as the scheduled path, pause and resume through IRecurringScheduleControl (GH-5168) by @​jeremydmiller in GH-5168 Timer-based recurring messages: one agent per short-cadence schedule JasperFx/wolverine#5183
• DoThenRetry(action, maxAttempts) error policy that works both inline and from a queue (GH-5068) by @​jeremydmiller in GH-5068 DoThenRetry() error policy that works inline and from a queue JasperFx/wolverine#5179
• Unmappable outgoing envelopes are dead-lettered on Azure Service Bus, SNS and Kafka instead of being reported as sent (GH-5055) by @​jeremydmiller in GH-5055 Dead letter outgoing envelopes a transport cannot map JasperFx/wolverine#5185
• Durable outbox coalesces stores and deletes per tenant database, so one slow tenant no longer holds back every tenant's sends (GH-5171) by @​jeremydmiller in GH-5171 Coalesce durable outbox/inbox writes per tenant database JasperFx/wolverine#5180
• 6.x prep for HandlerChain 1:1 in 7.0: MultipleHandlerBehavior.ClassicCombineIntoOneLogicalHandler is [Obsolete] (still the default), a startup warning for combined handlers, opt-in AssertNoCombinedHandlers(), fixes for latent Separated bugs, a handler.type OpenTelemetry tag on every chain, and logical deduplication scoped per chain (GH-5133) by @​jeremydmiller in GH-5133 6.x prep for 7.0's one chain per handler type: obsolete ClassicCombine, fix latent Separated bugs, per-handler OTel tag, per-chain dedup scoping JasperFx/wolverine#5184

HTTP

• [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes (GH-5160, GH-5165, GH-5166) by @​jeremydmiller with @​uniquelau in GH-5160, GH-5165, GH-5166: [DeduplicatedWithResponse] ClaimInTransaction, plus two Marten commit-failure fixes JasperFx/wolverine#5169
• WolverineHttpOptions.DefaultClaimInTransaction, an application-wide default (GH-5160) by @​jeremydmiller in GH-5160: WolverineHttpOptions.DefaultClaimInTransaction, a global opt-in for [DeduplicatedWithResponse(ClaimInTransaction)] JasperFx/wolverine#5173
• A string response declares its UTF-8 byte count as Content-Length (GH-5187) by @​johnkaram02 in GH-5187: a string response declares its UTF-8 byte count as Content-Length JasperFx/wolverine#5188
• Bind array and list query parameters whose [FromQuery] name is not a C# identifier (GH-5189) by @​johnkaram02 in GH-5189: bind array and list query parameters whose [FromQuery] name is not a C# identifier JasperFx/wolverine#5190

Operability and diagnostics

• ServiceCapabilities reads each store on its own and reports FailedSections, so a failed section is distinguishable from an empty one (GH-5162) by @​jeremydmiller in GH-5162 ServiceCapabilities: isolate each store, record FailedSections JasperFx/wolverine#5175
• AssignmentGrid.Agent.UnplacedReason (AwaitingCapacity, NoCapableNode, Paused, TakeoverHold, Superseded), a capacity log line and an optional NodeAcceptThreshold (GH-5163) by @​jeremydmiller in GH-5163 Unplaced agents carry an UnplacedReason; leader logs agents awaiting capacity JasperFx/wolverine#5176 and GH-5163 follow-up: UnplacedReason names are a stable contract; close the null-reason gaps JasperFx/wolverine#5186
• Header-equality filter on DeadLetterEnvelopeQuery, honored by bulk replay and discard, across every dead letter store (GH-5164) by @​jeremydmiller in GH-5164 DeadLetterEnvelopeQuery header-equality filter JasperFx/wolverine#5181
• db-list / db-dump / db-patch discover the Oracle message store (GH-5172) by @​jeremydmiller in GH-5172 Oracle message store is discoverable by the Weasel db-* commands JasperFx/wolverine#5177

Documentation

• The remaining serverless and Cosmos DB documentation (GH-5054) by @​jeremydmiller in GH-5054 Serverless docs: finish the remaining checklist items JasperFx/wolverine#5178
• Memory sizing for managed event subscription distribution at tenants x projections scale: set MaximumHopperSize to about 2 x BatchSize (GH-5170, follow-up JasperFx/jasperfx#​1076) by @​jeremydmiller in Bump to 6.52.0 JasperFx/wolverine#5199

Full Changelog: JasperFx/wolverine@V6.51.3...V6.52.0

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)