Bump the nuget-minor-and-patch group with 9 updates by dependabot[bot] · Pull Request #181 · sufyant/multi-tenant-saas-starter

dependabot · 2026-11-01T09:38:38Z

Updated OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Exporter.OpenTelemetryProtocol's releases.

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1-rc.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)
- Self-diagnostics messages written to the sinks configured by
  SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
  ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  made the server buffer a full copy of the response for each client that did
  not read it until the request completed or timed out. Responses are now
  written in bounded slices so the server's back-pressure applies.
  (#7957)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  on Linux and macOS made the listener allocate and hold a full copy of the
  response for each client that did not read it until the request completed or
  timed out. Responses are now written in bounded slices.
  (#7957)
- Fixed scrape requests that announce a request body holding a thread pool
  thread after their response had been sent on Linux and macOS for as long as
  the client kept trickling in the body. The connection is now closed after
  responding to a request with a body instead of being kept alive.
  (#7962)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Extensions.Hosting's releases.

1.20.1

For highlights and announcements pertaining to this release see: Release Notes > 1.20.1.

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)

... (truncated)

1.20.1-rc.1

The following changes are from the previous release 1.20.0.

NuGet: OpenTelemetry v1.20.1-rc.1
- Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, that could
  cause the measurement to be recorded incorrectly.
  (#7951)
- Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
  (#7955)
- Fixed default HTTP client log filtering when registering the OTLP log exporter
  through OpenTelemetryLoggerOptions.
  (#7959)
- Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or the log volume runs out of space.
  (#7956)
- Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
  (#7961)
- Fixed delta double counters losing subsequent measurements after a non-finite
  or large value and idle metric points with a NaN value failing to be reclaimed.
  (#7963)
- Improve the assignment of values to exponential histogram buckets when the
  value is near a bucket boundary by using a pre-computed lookup table.
  (#7911)
- Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early which could cause a BatchLogRecordExportProcessor
  on the same provider to export missing or incorrect data.
  (#7965)
- Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded, which caused
  all subsequent telemetry in that execution context to be suppressed.
  (#7966)
- Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
  (#7968)
- Self-diagnostics messages written to the sinks configured by
  SelfDiagnosticsOptions are now truncated to 16,384 characters so that the
  ... (truncated)

1.20.1-beta.1

The following changes are from the previous release 1.20.0-beta.1.

NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  made the server buffer a full copy of the response for each client that did
  not read it until the request completed or timed out. Responses are now
  written in bounded slices so the server's back-pressure applies.
  (#7957)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Prometheus.HttpListener v1.20.1-beta.1
- Fixed scrape responses being handed to the server in a single write, which
  on Linux and macOS made the listener allocate and hold a full copy of the
  response for each client that did not read it until the request completed or
  timed out. Responses are now written in bounded slices.
  (#7957)
- Fixed scrape requests that announce a request body holding a thread pool
  thread after their response had been sent on Linux and macOS for as long as
  the client kept trickling in the body. The connection is now closed after
  responding to a request with a body instead of being kept alive.
  (#7962)
- Fixed startup scrapes permanently omitting target_info and configured
  resource constant labels from subsequent scrape responses.
  (#7984)
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.
NuGet: OpenTelemetry.Shims.OpenTracing v1.20.1-beta.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#7990)
See CHANGELOG for details.

Commits viewable in compare view.

Updated OpenTelemetry.Instrumentation.AspNetCore from 1.20.0 to 1.20.1.

Release notes

Sourced from OpenTelemetry.Instrumentation.AspNetCore's releases.

1.20.1

NuGet: OpenTelemetry.Extensions.AWS v1.20.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#5651)
See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWS v1.20.1

No notable changes.

See CHANGELOG for details.
NuGet: OpenTelemetry.Instrumentation.AWSLambda v1.20.1

No notable changes.

See CHANGELOG for details.

1.20.1-rc.1

NuGet: OpenTelemetry.Instrumentation.Process v1.20.1-rc.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#5651)
See CHANGELOG for details.

1.20.1-beta.1

NuGet: OpenTelemetry.Extensions.Enrichment v1.20.1-beta.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#5651)
See CHANGELOG for details.

1.20.1-alpha.1

NuGet: OpenTelemetry.Instrumentation.EventCounters v1.20.1-alpha.1
- Updated OpenTelemetry core component version(s) to 1.20.1.
  (#5651)
See CHANGELOG for details.

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.18.0 to 2.18.3.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated WolverineFx from 6.51.0 to 6.53.0.

Release notes

Sourced from WolverineFx's releases.

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

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @billshuck, @dbelinsky-accureference, @endava-marinela-marchitan, @devployment, @kowalczb, @Patrick2607 and @ahmetvayhan.

Durable inbox hardening

Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
- A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
- Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
- EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
- A handler that calls ReScheduleAsync and then returns normally keeps its retry
- A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
- Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
- Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
- RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
GH-5108 Logical deduplication claim rides the EF Core transaction by @jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
GH-5116 A disposed message store refuses a dead letter instead of dropping it by @jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

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

6.51.2

Bug fix release on the JasperFx 2.91.0 / Marten 9.51.0 / Polecat 5.43.0 / Fisher 1.21.2 matched set, plus the Bobcat specification work

What's Changed

WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency by @jeremydmiller in WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency JasperFx/wolverine#5090
WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) by @jeremydmiller in WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) JasperFx/wolverine#5083
GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers by @jeremydmiller in GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers JasperFx/wolverine#5093
WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) by @jeremydmiller in WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) JasperFx/wolverine#5091
Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set by @jeremydmiller in Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set JasperFx/wolverine#5095
Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) by @lahma in Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) JasperFx/wolverine#5096
GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes by @jeremydmiller in GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes JasperFx/wolverine#5100
GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default by @jeremydmiller in GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default JasperFx/wolverine#5101
Don't dispose a DbDataSource the message store does not own by @lahma in Don't dispose a DbDataSource the message store does not own JasperFx/wolverine#5097
Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) by @jeremydmiller in Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) JasperFx/wolverine#5103
GH-5098 Event subscription capabilities match tenant-neutrally by @jeremydmiller in GH-5098 Event subscription capabilities match tenant-neutrally JasperFx/wolverine#5102
GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution by @jeremydmiller in GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution JasperFx/wolverine#5104

Committed directly to main

GH-5067 event-model --url stamps the pushed Event Model with its checkout root, repository and branch (dded67e95)
GH-5078 AgentAssignmentsChanged is obsolete, and the test observer's dead branch for it is removed (c1b22941a)

Full Changelog: JasperFx/wolverine@v6.51.1...V6.51.2

6.51.1

Bug fix release, and some doc updates too

What's Changed

GH-5070 A new leader keeps its own persisted leader row after a crash takeover by @jeremydmiller in GH-5070 A new leader keeps its own persisted leader row after a crash takeover JasperFx/wolverine#5071
Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure by @jeremydmiller in Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure JasperFx/wolverine#5074
Bobcat 1.0.0-rc.1 by @jeremydmiller in Bobcat 1.0.0-rc.1 JasperFx/wolverine#5079
GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes by @jeremydmiller in GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes JasperFx/wolverine#5084
GH-5085 Serverless docs: reword the 15 DRAFT comments into the page by @jeremydmiller in GH-5085 Serverless docs: reword the 15 DRAFT comments into the page JasperFx/wolverine#5086
GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) by @jeremydmiller in GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) JasperFx/wolverine#5081

Full Changelog: JasperFx/wolverine@V6.51.0...v6.51.1

Commits viewable in compare view.

Updated WolverineFx.EntityFrameworkCore from 6.51.0 to 6.53.0.

Release notes

Sourced from WolverineFx.EntityFrameworkCore's releases.

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

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @billshuck, @dbelinsky-accureference, @endava-marinela-marchitan, @devployment, @kowalczb, @Patrick2607 and @ahmetvayhan.

Durable inbox hardening

Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
- A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
- Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
- EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
- A handler that calls ReScheduleAsync and then returns normally keeps its retry
- A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
- Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
- Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
- RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
GH-5108 Logical deduplication claim rides the EF Core transaction by @jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
GH-5116 A disposed message store refuses a dead letter instead of dropping it by @jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

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

6.51.2

Bug fix release on the JasperFx 2.91.0 / Marten 9.51.0 / Polecat 5.43.0 / Fisher 1.21.2 matched set, plus the Bobcat specification work

What's Changed

WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency by @jeremydmiller in WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency JasperFx/wolverine#5090
WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) by @jeremydmiller in WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) JasperFx/wolverine#5083
GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers by @jeremydmiller in GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers JasperFx/wolverine#5093
WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) by @jeremydmiller in WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) JasperFx/wolverine#5091
Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set by @jeremydmiller in Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set JasperFx/wolverine#5095
Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) by @lahma in Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) JasperFx/wolverine#5096
GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes by @jeremydmiller in GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes JasperFx/wolverine#5100
GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default by @jeremydmiller in GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default JasperFx/wolverine#5101
Don't dispose a DbDataSource the message store does not own by @lahma in Don't dispose a DbDataSource the message store does not own JasperFx/wolverine#5097
Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) by @jeremydmiller in Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) JasperFx/wolverine#5103
GH-5098 Event subscription capabilities match tenant-neutrally by @jeremydmiller in GH-5098 Event subscription capabilities match tenant-neutrally JasperFx/wolverine#5102
GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution by @jeremydmiller in GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution JasperFx/wolverine#5104

Committed directly to main

GH-5067 event-model --url stamps the pushed Event Model with its checkout root, repository and branch (dded67e95)
GH-5078 AgentAssignmentsChanged is obsolete, and the test observer's dead branch for it is removed (c1b22941a)

Full Changelog: JasperFx/wolverine@v6.51.1...V6.51.2

6.51.1

Bug fix release, and some doc updates too

What's Changed

GH-5070 A new leader keeps its own persisted leader row after a crash takeover by @jeremydmiller in GH-5070 A new leader keeps its own persisted leader row after a crash takeover JasperFx/wolverine#5071
Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure by @jeremydmiller in Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure JasperFx/wolverine#5074
Bobcat 1.0.0-rc.1 by @jeremydmiller in Bobcat 1.0.0-rc.1 JasperFx/wolverine#5079
GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes by @jeremydmiller in GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes JasperFx/wolverine#5084
GH-5085 Serverless docs: reword the 15 DRAFT comments into the page by @jeremydmiller in GH-5085 Serverless docs: reword the 15 DRAFT comments into the page JasperFx/wolverine#5086
GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) by @jeremydmiller in GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) JasperFx/wolverine#5081

Full Changelog: JasperFx/wolverine@V6.51.0...v6.51.1

Commits viewable in compare view.

Updated WolverineFx.FluentValidation from 6.51.0 to 6.53.0.

Release notes

Sourced from WolverineFx.FluentValidation's releases.

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

6.51.3

Wolverine 6.51.3 is a durability release. Nearly everything in it came out of a run of reports against the durable inbox and outbox, plus a new durable receiver compliance rig (src/Testing/DurableComplianceRig, Bobcat specs across PostgreSQL, SQL Server, Marten and EF Core over local, database, RabbitMQ and SQS endpoints) that turned up the rest. There are no breaking API changes; the one schema addition (a nullable envelope_id column on the deduplication table) is optional and an unmigrated table keeps working.

Many thanks to everyone who reported these with reproductions: @billshuck, @dbelinsky-accureference, @endava-marinela-marchitan, @devployment, @kowalczb, @Patrick2607 and @ahmetvayhan.

Durable inbox hardening

Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split by @jeremydmiller in Durable inbox hardening, part 1: transactions, idempotency, deduplication, GH-5123 and the CISqlServer split JasperFx/wolverine#5129
- A late DbTransaction dispose in MessageContext.ClearState() could kill another handler's Npgsql transaction
- Eager idempotency now writes its placeholder inside the handler's transaction (Marten, EF Core, Polecat, Fisher), so a requeued failure is no longer dead lettered as a duplicate of itself
- EF Core marks the inbox row Handled only after its own commit, and inside the tenant transaction for database-per-tenant
- A handler that calls ReScheduleAsync and then returns normally keeps its retry
- A [Deduplicated] claim stranded by a crash can be taken over by the same envelope (new nullable envelope_id column, opt-in IEnvelopeAwareDeduplicationStore)
- Envelope.DeduplicationId now crosses RabbitMQ, the generic EnvelopeMapper brokers and MQTT
- Two copies of one envelope in a single batch are reported as DuplicateIncomingEnvelopeException instead of pausing the listener or tripping the tenant write brake (PostgreSQL, SQL Server, MySQL, SQLite, Oracle)
- RabbitMQ quorum queues: opt-in x-delivery-limit (.DeliveryLimit(n), DeliveryLimitForDurableQuorumQueues(n)), a startup warning, and DeferAsync publishes before it acks. New docs section "Quorum Queues and the Durable Inbox"
Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues by @jeremydmiller in Durable receiver hardening, part 2: batch member settlement, inbox ownership, paused local queues JasperFx/wolverine#5157
Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) by @jeremydmiller in Durable receiver hardening, part 3: drain release vs. a new receiver's first claim; heartbeat only while holding (F18) JasperFx/wolverine#5158

Durable bug fixes

GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 PostgreSQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5109
GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQL Server queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5112
GH-5107 MySQL queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 MySQL queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5113
GH-5107 Oracle queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 Oracle queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5114
GH-5107 SQLite queue sender moves the outbox row atomically for every durable send by @jeremydmiller in GH-5107 SQLite queue sender moves the outbox row atomically for every durable send JasperFx/wolverine#5115
GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered by @jeremydmiller in GH-5105 Durable receiver awaits the dead-letter write; a failed write is never reported as dead lettered JasperFx/wolverine#5110
GH-5108 Logical deduplication claim rides the EF Core transaction by @jeremydmiller in GH-5108 Logical deduplication claim rides the EF Core transaction JasperFx/wolverine#5111
GH-5116 A disposed message store refuses a dead letter instead of dropping it by @jeremydmiller in GH-5116 A disposed message store refuses a dead letter instead of dropping it JasperFx/wolverine#5118
GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked (durable SQS listeners since 6.40.0) by @jeremydmiller in GH-5119 Durable receivers settle the inbox row even when the broker delivery is already acked JasperFx/wolverine#5121
GH-5120 A durable batch's scheduled retry is held in memory instead of lost by @jeremydmiller in GH-5120 A durable batch's scheduled retry is held in memory instead of lost JasperFx/wolverine#5122

Testing

GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids by @jeremydmiller in GH-5106 Bobcat failure reports carry the message, correlation, causation and trace ids JasperFx/wolverine#5117

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

6.51.2

Bug fix release on the JasperFx 2.91.0 / Marten 9.51.0 / Polecat 5.43.0 / Fisher 1.21.2 matched set, plus the Bobcat specification work

What's Changed

WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency by @jeremydmiller in WolverineFx.ComplianceTests suppresses NU5104 for its prerelease Bobcat dependency JasperFx/wolverine#5090
WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) by @jeremydmiller in WolverineFx.Bobcat takes the Critter Stack vocabulary, Bobcat's samples and the spec writer (#5082) JasperFx/wolverine#5083
GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers by @jeremydmiller in GH-5087 Database queue listeners: deferral survives stop; SQLite StopAsync joins its workers JasperFx/wolverine#5093
WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) by @jeremydmiller in WolverineFx.Bobcat: scheduled messages are explicit (#5077); ThenHandled, scheduled grammars, body-less HTTP acts, GivenReceived (#5076) JasperFx/wolverine#5091
Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set by @jeremydmiller in Wolverine 6.51.2: GH-5092 coordinator only observes, GH-5087 MySQL/Oracle join, JasperFx 2.91.0 matched set JasperFx/wolverine#5095
Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) by @lahma in Keep a blocking receive loop on its dedicated thread past the first await (GH-4330 follow-up) JasperFx/wolverine#5096
GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes by @jeremydmiller in GH-5089 Event Model: match the EmittedEvents manifest to a handler overload by its ParameterTypes JasperFx/wolverine#5100
GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default by @jeremydmiller in GH-5099 Wolverine.HTTP: an omitted query, header or form value binds the parameter's declared default JasperFx/wolverine#5101
Don't dispose a DbDataSource the message store does not own by @lahma in Don't dispose a DbDataSource the message store does not own JasperFx/wolverine#5097
Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) by @jeremydmiller in Docs: Specifications with Bobcat (WolverineFx.Bobcat reference page) JasperFx/wolverine#5103
GH-5098 Event subscription capabilities match tenant-neutrally by @jeremydmiller in GH-5098 Event subscription capabilities match tenant-neutrally JasperFx/wolverine#5102
GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution by @jeremydmiller in GH-5094 Wolverine.Fisher: opt-in Wolverine-managed event subscription distribution JasperFx/wolverine#5104

Committed directly to main

GH-5067 event-model --url stamps the pushed Event Model with its checkout root, repository and branch (dded67e95)
GH-5078 AgentAssignmentsChanged is obsolete, and the test observer's dead branch for it is removed (c1b22941a)

Full Changelog: JasperFx/wolverine@v6.51.1...V6.51.2

6.51.1

Bug fix release, and some doc updates too

What's Changed

GH-5070 A new leader keeps its own persisted leader row after a crash takeover by @jeremydmiller in GH-5070 A new leader keeps its own persisted leader row after a crash takeover JasperFx/wolverine#5071
Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure by @jeremydmiller in Leadership-election compliance on Bobcat, with agent-assignment telemetry on failure JasperFx/wolverine#5074
Bobcat 1.0.0-rc.1 by @jeremydmiller in Bobcat 1.0.0-rc.1 JasperFx/wolverine#5079
GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes by @jeremydmiller in GH-5080 CloudEvents carries lower case Envelope.Headers as extension attributes JasperFx/wolverine#5084
GH-5085 Serverless docs: reword the 15 DRAFT comments into the page by @jeremydmiller in GH-5085 Serverless docs: reword the 15 DRAFT comments into the page JasperFx/wolverine#5086
GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) by @jeremydmiller in GH-5073 Atomic, deadlock-free inbox recovery claims on every store (supersedes #5075) JasperFx/wolverine#5081

Full Changelog: JasperFx/wolverine@V6.51.0...v6.51.1

Commits viewable in compare view.

Updated WolverineFx.Postgresql from 6.51.0 to 6.53.0.

Release notes

Sourced from WolverineFx.Postgresql's releases.

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 ...

Description has been truncated

Bumps OpenTelemetry.Exporter.OpenTelemetryProtocol from 1.20.0 to 1.20.1 Bumps OpenTelemetry.Extensions.Hosting from 1.20.0 to 1.20.1 Bumps OpenTelemetry.Instrumentation.AspNetCore from 1.20.0 to 1.20.1 Bumps Scalar.AspNetCore from 2.18.0 to 2.18.3 Bumps WolverineFx from 6.51.0 to 6.53.0 Bumps WolverineFx.EntityFrameworkCore from 6.51.0 to 6.53.0 Bumps WolverineFx.FluentValidation from 6.51.0 to 6.53.0 Bumps WolverineFx.Postgresql from 6.51.0 to 6.53.0 Bumps WolverineFx.RuntimeCompilation from 6.51.0 to 6.53.0 --- updated-dependencies: - dependency-name: OpenTelemetry.Exporter.OpenTelemetryProtocol dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: OpenTelemetry.Extensions.Hosting dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: OpenTelemetry.Instrumentation.AspNetCore dependency-version: 1.20.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: Scalar.AspNetCore dependency-version: 2.18.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx dependency-version: 6.53.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.EntityFrameworkCore dependency-version: 6.53.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.FluentValidation dependency-version: 6.53.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.Postgresql dependency-version: 6.53.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch - dependency-name: WolverineFx.RuntimeCompilation dependency-version: 6.53.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget-minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>

dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 1, 2026

Navigation Menu

Repository navigation

Bump the nuget-minor-and-patch group with 9 updates - #181

Bump the nuget-minor-and-patch group with 9 updates#181
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/apps/api/nuget-minor-and-patch-b4a7170ad2

dependabot Bot commented on behalf of github Nov 1, 2026

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

dependabot Bot commented on behalf of github Nov 1, 2026

1.20.1

1.20.1-rc.1

1.20.1-beta.1

1.20.1

1.20.1-rc.1

1.20.1-beta.1

1.20.1

1.20.1-rc.1

1.20.1-beta.1

1.20.1-alpha.1

6.53.0

What's Changed

New Contributors

6.52.0

Aspire parity: named connections

Messaging and error handling

HTTP

Operability and diagnostics

Documentation

6.51.3

Durable inbox hardening

Durable bug fixes

Testing

6.51.2

What's Changed

Committed directly to main

6.51.1

What's Changed

6.53.0

What's Changed

New Contributors

6.52.0

Aspire parity: named connections

Messaging and error handling

HTTP

Operability and diagnostics

Documentation

6.51.3

Durable inbox hardening

Durable bug fixes

Testing

6.51.2

What's Changed

Committed directly to main

6.51.1

What's Changed

6.53.0

What's Changed

New Contributors

6.52.0

Aspire parity: named connections

Messaging and error handling

HTTP

Operability and diagnostics

Documentation

6.51.3

Durable inbox hardening

Durable bug fixes

Testing

6.51.2

What's Changed

Committed directly to main

6.51.1

What's Changed

6.53.0

What's Changed

New Contributors

6.52.0

Aspire parity: named connections

Uh oh!

This branch has not been deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development