Repository navigation
GH-5353 ProblemDetails factory for the 409 conflict mapping - #5370
Merged
Merged
Conversation
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This was referenced Nov 6, 2026
This was referenced Nov 10, 2026
github-actions Bot
pushed a commit
to MrD4rkne/oweme-ecosystem
that referenced
this pull request
Nov 13, 2026
Updated [Aspire.Hosting.AppHost](https://github.com/microsoft/aspire)
from 13.6.4 to 13.6.5.
<details>
<summary>Release notes</summary>
_Sourced from [Aspire.Hosting.AppHost's
releases](https://github.com/microsoft/aspire/releases)._
## 13.6.5
## What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening
and .NET runtime servicing updates.
### 🐛 Fixes
- 🖥️ **Dashboard authentication is enforced on missing and unauthorized
routes** — Secured dashboards now check authorization before rendering
the main layout for missing routes or denied access. In browser-token
mode, unauthenticated users are redirected to login with the original
route preserved. Additional authentication checks protect layout,
dialog, interaction, and standalone terminal-window initialization;
unsecured mode is unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[0b6bfe2](https://github.com/microsoft/aspire/commit/0b6bfe2f538d4eed8a9ae7e11651c09dbbe886b8),
@jamesnk)
- 🔒 **Container telemetry no longer implicitly exposes the dashboard
frontend** — When the Aspire container tunnel is enabled, automatic
dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints.
Explicit references to other dashboard endpoints remain supported, and
tunneling for ordinary host-resource dependencies is unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[f017f66](https://github.com/microsoft/aspire/commit/f017f668fd6e0938e23058dc0450a1403f409809),
@karolz-ms)
- 🔒 **CLI-generated builds and SDK working directories are isolated** —
Generated AppHost server and integration builds now ignore automatic
MSBuild response files without changing user-authored builds or support
for explicitly supplied response files. The `aspire sdk generate`,
`aspire sdk dump`, and `aspire sdk export` commands use isolated working
directories under `<ASPIRE_HOME>/tmp/sdk/<unique-id>`, with owner-only
Unix permissions, local configuration isolation, and cleanup when the
command finishes. Normal AppHost caches are unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[1ecd7cc](https://github.com/microsoft/aspire/commit/1ecd7cc70b5a5a5b8571fe3af69faa1646b8de47),
@sebastienros)
- 🔒 **Agent setup no longer writes configuration content to a shared
temporary log** — `aspire agent init` stops writing agent configuration
paths, configuration content, and scan diagnostics to
`aspire-deprecated-scan.log` in the operating system's temporary
directory. Deprecated MCP command detection, migration prompts,
configuration updates, and existing structured debug logging are
preserved. Previously written temporary log files are not removed by
this update. ([#22071](https://github.com/microsoft/aspire/pull/22071),
[c408ec5](https://github.com/microsoft/aspire/commit/c408ec5bf44e43203c278990a43aea93145248f3),
@mitchdenny)
- 🛠️ **Updated .NET runtimes and dependencies for startup reliability**
— Refreshes bundled runtimes and .NET servicing dependencies, including
.NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to
Native AOT process startup.
([#21348](https://github.com/microsoft/aspire/pull/21348), @joperezr)
---
*Full Changelog:
[v13.6.4...v13.6.5](https://github.com/microsoft/aspire/compare/v13.6.4...v13.6.5)*
*Full commit:
[b33d222049f1ecc3bc7257ec07b622fe550b2580](https://github.com/microsoft/aspire/commit/b33d222049f1ecc3bc7257ec07b622fe550b2580)*
Commits viewable in [compare
view](https://github.com/microsoft/aspire/compare/v13.6.4...v13.6.5).
</details>
Updated [Aspire.Hosting.PostgreSQL](https://github.com/microsoft/aspire)
from 13.6.4 to 13.6.5.
<details>
<summary>Release notes</summary>
_Sourced from [Aspire.Hosting.PostgreSQL's
releases](https://github.com/microsoft/aspire/releases)._
## 13.6.5
## What's New in Aspire 13.6.5
Patch release for Aspire 13.6 with dashboard and CLI security hardening
and .NET runtime servicing updates.
### 🐛 Fixes
- 🖥️ **Dashboard authentication is enforced on missing and unauthorized
routes** — Secured dashboards now check authorization before rendering
the main layout for missing routes or denied access. In browser-token
mode, unauthenticated users are redirected to login with the original
route preserved. Additional authentication checks protect layout,
dialog, interaction, and standalone terminal-window initialization;
unsecured mode is unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[0b6bfe2](https://github.com/microsoft/aspire/commit/0b6bfe2f538d4eed8a9ae7e11651c09dbbe886b8),
@jamesnk)
- 🔒 **Container telemetry no longer implicitly exposes the dashboard
frontend** — When the Aspire container tunnel is enabled, automatic
dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints.
Explicit references to other dashboard endpoints remain supported, and
tunneling for ordinary host-resource dependencies is unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[f017f66](https://github.com/microsoft/aspire/commit/f017f668fd6e0938e23058dc0450a1403f409809),
@karolz-ms)
- 🔒 **CLI-generated builds and SDK working directories are isolated** —
Generated AppHost server and integration builds now ignore automatic
MSBuild response files without changing user-authored builds or support
for explicitly supplied response files. The `aspire sdk generate`,
`aspire sdk dump`, and `aspire sdk export` commands use isolated working
directories under `<ASPIRE_HOME>/tmp/sdk/<unique-id>`, with owner-only
Unix permissions, local configuration isolation, and cleanup when the
command finishes. Normal AppHost caches are unchanged.
([#22071](https://github.com/microsoft/aspire/pull/22071),
[1ecd7cc](https://github.com/microsoft/aspire/commit/1ecd7cc70b5a5a5b8571fe3af69faa1646b8de47),
@sebastienros)
- 🔒 **Agent setup no longer writes configuration content to a shared
temporary log** — `aspire agent init` stops writing agent configuration
paths, configuration content, and scan diagnostics to
`aspire-deprecated-scan.log` in the operating system's temporary
directory. Deprecated MCP command detection, migration prompts,
configuration updates, and existing structured debug logging are
preserved. Previously written temporary log files are not removed by
this update. ([#22071](https://github.com/microsoft/aspire/pull/22071),
[c408ec5](https://github.com/microsoft/aspire/commit/c408ec5bf44e43203c278990a43aea93145248f3),
@mitchdenny)
- 🛠️ **Updated .NET runtimes and dependencies for startup reliability**
— Refreshes bundled runtimes and .NET servicing dependencies, including
.NET 10.0.14, 9.0.22, and 8.0.33, to pick up servicing fixes relevant to
Native AOT process startup.
([#21348](https://github.com/microsoft/aspire/pull/21348), @joperezr)
---
*Full Changelog:
[v13.6.4...v13.6.5](https://github.com/microsoft/aspire/compare/v13.6.4...v13.6.5)*
*Full commit:
[b33d222049f1ecc3bc7257ec07b622fe550b2580](https://github.com/microsoft/aspire/commit/b33d222049f1ecc3bc7257ec07b622fe550b2580)*
Commits viewable in [compare
view](https://github.com/microsoft/aspire/compare/v13.6.4...v13.6.5).
</details>
Updated
[Microsoft.AspNetCore.Authentication.JwtBearer](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.AspNetCore.Authentication.JwtBearer's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.AspNetCore.Mvc.Testing](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.AspNetCore.Mvc.Testing's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated [Microsoft.AspNetCore.OpenApi](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.AspNetCore.OpenApi's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated [Microsoft.Bcl.TimeProvider](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Bcl.TimeProvider's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.EntityFrameworkCore](https://github.com/dotnet/dotnet) from
10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.EntityFrameworkCore's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.EntityFrameworkCore.Abstractions](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.EntityFrameworkCore.Abstractions's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.EntityFrameworkCore.Design](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.EntityFrameworkCore.Design's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.EntityFrameworkCore.Tools](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.EntityFrameworkCore.Tools's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.ApiDescription.Server](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.ApiDescription.Server's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.Caching.Memory](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Caching.Memory's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.Configuration.EnvironmentVariables](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Configuration.EnvironmentVariables's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.Configuration.Json](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Configuration.Json's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.DependencyInjection.Abstractions](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.DependencyInjection.Abstractions's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from
[Microsoft.Extensions.Diagnostics.HealthChecks.EntityFrameworkCore's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated
[Microsoft.Extensions.Hosting.Abstractions](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Hosting.Abstractions's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated [Microsoft.Extensions.Http](https://github.com/dotnet/dotnet)
from 10.0.14 to 10.0.15.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.Extensions.Http's
releases](https://github.com/dotnet/dotnet/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/dotnet/dotnet/commits).
</details>
Updated [Microsoft.NET.Test.Sdk](https://github.com/microsoft/vstest)
from 17.14.1 to 17.14.2.
<details>
<summary>Release notes</summary>
_Sourced from [Microsoft.NET.Test.Sdk's
releases](https://github.com/microsoft/vstest/releases)._
## 17.14.2
## Security fix
This release fixes CVE-2026-105544, an elevation of privilege
vulnerability in the VSTest artifact post-processor. The post-processor
could consume a forged `executionComplete.json` written by another local
user, and then run attacker-controlled output handling.
Affected: `Microsoft.TestPlatform.CLI` 17.14.0 and 17.14.1.
Fixed in: `Microsoft.TestPlatform.CLI` 17.14.2.
`Microsoft.TestPlatform.CLI` is the VSTest build that we ship into the
.NET SDK. The recommended way to get this fix is to update your .NET SDK
to the latest patched version, see the advisory for the SDK versions.
The fix is also released in the `Microsoft.TestPlatform.CLI` package,
for completeness. That package is rarely used directly. It is not a
dependency of `Microsoft.NET.Test.Sdk` or `Microsoft.TestPlatform`, so
those packages do not bring it in.
Details: https://github.com/microsoft/vstest/issues/16654 and
https://github.com/dotnet/announcements/issues/517
Using custom Docker images or Nano Server? See
https://github.com/microsoft/vstest/issues/16652
## What's Changed
* Security fix for CVE-2026-105544, see
https://github.com/microsoft/vstest/issues/16654
**Full Changelog**:
https://github.com/microsoft/vstest/compare/v17.14.1...v17.14.2
Commits viewable in [compare
view](https://github.com/microsoft/vstest/compare/v17.14.1...v17.14.2).
</details>
Updated
[OpenTelemetry.Instrumentation.AspNetCore](https://github.com/open-telemetry/opentelemetry-dotnet-contrib)
from 1.20.1 to 1.20.2.
<details>
<summary>Release notes</summary>
_Sourced from [OpenTelemetry.Instrumentation.AspNetCore's
releases](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/releases)._
## 1.20.2
* NuGet: [OpenTelemetry.Extensions.AWS
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Extensions.AWS/1.20.2)
No notable changes.
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Extensions.AWS/CHANGELOG.md)
for details.
* NuGet: [OpenTelemetry.Instrumentation.AWS
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWS/1.20.2)
No notable changes.
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Instrumentation.AWS/CHANGELOG.md)
for details.
* NuGet: [OpenTelemetry.Instrumentation.AWSLambda
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWSLambda/1.20.2)
* Fix `server.address` and `server.port` not being recorded correctly
for HTTP
requests with an IPv6 address in the `Host` header (e.g. `[::1]:8080`).
([#5788](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5788))
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Instrumentation.AWSLambda/CHANGELOG.md)
for details.
## 1.20.2-beta.1
* NuGet: [OpenTelemetry.Instrumentation.Hangfire
v1.20.2-beta.1](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.Hangfire/1.20.2-beta.1)
* Fixed failed jobs exporting the exception message as the span status
description.
The message is now only recorded when `RecordException` is enabled.
([#5884](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5884))
* Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
([#5886](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5886))
* Added `EnrichWithBackgroundJob` and `CustomStateMappings` to
`HangfireMetricsInstrumentationOptions`. Use them to add custom
attributes to
the metrics and to count jobs in custom Hangfire states.
([#5810](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5810))
* Fixed `workflow.execution.duration` for the `executing` state. It
included the
time of other measurements of this instrumentation, for example the
database
query that `RecordQueueLatency` adds.
([#5810](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5810))
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.Hangfire-1.20.2-beta.1/src/OpenTelemetry.Instrumentation.Hangfire/CHANGELOG.md)
for details.
Commits viewable in [compare
view](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/compare/Exporter.Geneva-1.20.1...Instrumentation.AWS-1.20.2).
</details>
Updated
[OpenTelemetry.Instrumentation.Http](https://github.com/open-telemetry/opentelemetry-dotnet-contrib)
from 1.20.1 to 1.20.2.
<details>
<summary>Release notes</summary>
_Sourced from [OpenTelemetry.Instrumentation.Http's
releases](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/releases)._
## 1.20.2
* NuGet: [OpenTelemetry.Extensions.AWS
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Extensions.AWS/1.20.2)
No notable changes.
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Extensions.AWS/CHANGELOG.md)
for details.
* NuGet: [OpenTelemetry.Instrumentation.AWS
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWS/1.20.2)
No notable changes.
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Instrumentation.AWS/CHANGELOG.md)
for details.
* NuGet: [OpenTelemetry.Instrumentation.AWSLambda
v1.20.2](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.AWSLambda/1.20.2)
* Fix `server.address` and `server.port` not being recorded correctly
for HTTP
requests with an IPv6 address in the `Host` header (e.g. `[::1]:8080`).
([#5788](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5788))
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.AWS-1.20.2/src/OpenTelemetry.Instrumentation.AWSLambda/CHANGELOG.md)
for details.
## 1.20.2-beta.1
* NuGet: [OpenTelemetry.Instrumentation.Hangfire
v1.20.2-beta.1](https://www.nuget.org/packages/OpenTelemetry.Instrumentation.Hangfire/1.20.2-beta.1)
* Fixed failed jobs exporting the exception message as the span status
description.
The message is now only recorded when `RecordException` is enabled.
([#5884](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5884))
* Fixed baggage from a job being visible to work started by other jobs
performed on the same worker.
([#5886](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5886))
* Added `EnrichWithBackgroundJob` and `CustomStateMappings` to
`HangfireMetricsInstrumentationOptions`. Use them to add custom
attributes to
the metrics and to count jobs in custom Hangfire states.
([#5810](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5810))
* Fixed `workflow.execution.duration` for the `executing` state. It
included the
time of other measurements of this instrumentation, for example the
database
query that `RecordQueueLatency` adds.
([#5810](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/5810))
See
[CHANGELOG](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/Instrumentation.Hangfire-1.20.2-beta.1/src/OpenTelemetry.Instrumentation.Hangfire/CHANGELOG.md)
for details.
Commits viewable in [compare
view](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/compare/Exporter.Geneva-1.20.1...Instrumentation.AWS-1.20.2).
</details>
Updated [Scalar.AspNetCore](https://github.com/scalar/scalar) from
2.18.7 to 2.20.0.
<details>
<summary>Release notes</summary>
_Sourced from [Scalar.AspNetCore's
releases](https://github.com/scalar/scalar/releases)._
No release notes found for this version range.
Commits viewable in [compare
view](https://github.com/scalar/scalar/commits).
</details>
Updated [WolverineFx](http://github.com/jasperfx/wolverine) from 6.61.0
to 6.64.0.
<details>
<summary>Release notes</summary>
_Sourced from [WolverineFx's
releases](http://github.com/jasperfx/wolverine/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
* Bump JasperFx to 2.101.0 and Weasel to 9.50.0; document the command
line under Native AOT by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5442
* Docs: the resource setup hosted service migrates message storage
regardless of AutoCreate by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5445
* GH-5443 Release lease and idempotency state for envelopes settled in
DeserializeFirst by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5448
* Bump JasperFx to 2.102.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5449
* GH-5446 Raise IWolverineObserver.CircuitBreakerReset when a
breaker-paused listener accepts again by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5451
* GH-5452: Rabbit MQ keeps one reply queue across `ResetResourceState()`
calls by @alesdvorakcz in
https://github.com/JasperFx/wolverine/pull/5453
* Bump version to 6.64.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5454
**Full Changelog**:
https://github.com/JasperFx/wolverine/compare/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
* Keep the inbox id of a durable envelope when a CloudEvent with a Guid
id is read from its data by @lahma in
https://github.com/JasperFx/wolverine/pull/5396
* GH-5395 A dead letter marked replayable mid-move is no longer deleted
without reaching the inbox by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5397
* MassTransit interop keeps the inbox id of a durable envelope when it
reads the messageId by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5398
* Default envelope ids no longer collide between processes on one
machine by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5399
* Scheduled retries on the SQL Server, MySQL, Oracle and SQLite queues
are atomic by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5408
* GH-5406 HTTP span tags are written before anything can short-circuit
the request by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5418
* GH-5416 Document waiting on a message the broker fans out to several
queues by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5419
* GH-5409 Commit the out-of-process durability chaos rig with a README
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5420
* GH-5411 A durable pop skips envelopes the inbox already holds instead
of rolling the batch back by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5421
* GH-5412 The SQL Server scheduled-message poll never waits on a lock by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5422
* GH-5413 A database queue drains a backlog without waiting a polling
interval per batch by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5424
* GH-5410 A commit that applied but reported an error is not
dead-lettered and its cascades run by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5425
* GH-5423 A node resumed after being ejected as stale does not commit
work another node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5427
* GH-5428 The MySQL expired-handled cleanup no longer locks live inbox
rows by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5431
* GH-5429 Oracle's in-transaction mark-as-handled refuses work another
node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5432
* GH-5430 SQLite in Balanced mode assigns node numbers and reads health
checks as UTC by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5433
* GH-5426 A scheduled retry on a database queue is fenced on the inbox
row's owner by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5434
* GH-5435 Tenant databases with one name on one host are told apart by
port by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5436
* GH-5438 The outbox-to-queue move is one transaction on MySQL, SQL
Server and SQLite by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5439
* Docs: schema management options for message storage, linked to Weasel
and the stateful resource model by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5437
* GH-5414 Durability chaos rig, round three by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5440
* Bump version to 6.63.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5441
... (truncated)
## 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
* GH-5069 [SagaIsResponseOnly] for endpoints returning a saga as the
response by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5366
* GH-5088 PublishOnlyToShardedPostgresqlQueues (no listeners) by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5367
* GH-5207 EF Core transactional middleware: configurable isolation level
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5369
* GH-5342 Azure Service Bus: support externally owned topics by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5368
* GH-5353 ProblemDetails factory for the 409 conflict mapping by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5370
* feat(kafka): allow setting replay group id by @Mr444-dev in
https://github.com/JasperFx/wolverine/pull/5343
* GH-5346 PostgreSQL scheduled-message poll gets the index SQL Server
has by @uniquelau in https://github.com/JasperFx/wolverine/pull/5347
* GH-5348 DurableLocalQueue.StartAsync skips an accepting queue and is
serialized by @uniquelau in
https://github.com/JasperFx/wolverine/pull/5349
* docs: circuit breakers and error policies in tests by @uniquelau in
https://github.com/JasperFx/wolverine/pull/5350
* Describe query parameters with their data annotations in OpenAPI by
@esond in https://github.com/JasperFx/wolverine/pull/5351
* [DeduplicatedWithResponse] replays ASP.NET Core IResult responses by
@esond in https://github.com/JasperFx/wolverine/pull/5352
* Merge OnException handlers for the same exception type into one catch
clause by @esond in https://github.com/JasperFx/wolverine/pull/5357
* Follow-ups: Kafka replay GroupId docs + kafka-replay --group-id
(#5306), same-type OnException docs (#5357) by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5380
* GH-5364 CloudEventsMapper keeps envelope id on re-read; stable id for
non-Guid CloudEvent ids by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5377
* GH-5361 scaffold: multi-event automation becomes one handler class by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5375
* GH-5360 scaffold: don't plan every emitted event as an Apply on every
stream by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5374
... (truncated)
Commits viewable in [compare
view](http://github.com/jasperfx/wolverine/compare/V6.61.0...V6.64.0).
</details>
Updated
[WolverineFx.FluentValidation](http://github.com/jasperfx/wolverine)
from 6.61.0 to 6.64.0.
<details>
<summary>Release notes</summary>
_Sourced from [WolverineFx.FluentValidation's
releases](http://github.com/jasperfx/wolverine/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
* Bump JasperFx to 2.101.0 and Weasel to 9.50.0; document the command
line under Native AOT by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5442
* Docs: the resource setup hosted service migrates message storage
regardless of AutoCreate by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5445
* GH-5443 Release lease and idempotency state for envelopes settled in
DeserializeFirst by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5448
* Bump JasperFx to 2.102.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5449
* GH-5446 Raise IWolverineObserver.CircuitBreakerReset when a
breaker-paused listener accepts again by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5451
* GH-5452: Rabbit MQ keeps one reply queue across `ResetResourceState()`
calls by @alesdvorakcz in
https://github.com/JasperFx/wolverine/pull/5453
* Bump version to 6.64.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5454
**Full Changelog**:
https://github.com/JasperFx/wolverine/compare/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
* Keep the inbox id of a durable envelope when a CloudEvent with a Guid
id is read from its data by @lahma in
https://github.com/JasperFx/wolverine/pull/5396
* GH-5395 A dead letter marked replayable mid-move is no longer deleted
without reaching the inbox by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5397
* MassTransit interop keeps the inbox id of a durable envelope when it
reads the messageId by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5398
* Default envelope ids no longer collide between processes on one
machine by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5399
* Scheduled retries on the SQL Server, MySQL, Oracle and SQLite queues
are atomic by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5408
* GH-5406 HTTP span tags are written before anything can short-circuit
the request by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5418
* GH-5416 Document waiting on a message the broker fans out to several
queues by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5419
* GH-5409 Commit the out-of-process durability chaos rig with a README
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5420
* GH-5411 A durable pop skips envelopes the inbox already holds instead
of rolling the batch back by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5421
* GH-5412 The SQL Server scheduled-message poll never waits on a lock by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5422
* GH-5413 A database queue drains a backlog without waiting a polling
interval per batch by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5424
* GH-5410 A commit that applied but reported an error is not
dead-lettered and its cascades run by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5425
* GH-5423 A node resumed after being ejected as stale does not commit
work another node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5427
* GH-5428 The MySQL expired-handled cleanup no longer locks live inbox
rows by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5431
* GH-5429 Oracle's in-transaction mark-as-handled refuses work another
node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5432
* GH-5430 SQLite in Balanced mode assigns node numbers and reads health
checks as UTC by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5433
* GH-5426 A scheduled retry on a database queue is fenced on the inbox
row's owner by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5434
* GH-5435 Tenant databases with one name on one host are told apart by
port by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5436
* GH-5438 The outbox-to-queue move is one transaction on MySQL, SQL
Server and SQLite by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5439
* Docs: schema management options for message storage, linked to Weasel
and the stateful resource model by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5437
* GH-5414 Durability chaos rig, round three by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5440
* Bump version to 6.63.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5441
... (truncated)
## 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
* GH-5069 [SagaIsResponseOnly] for endpoints returning a saga as the
response by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5366
* GH-5088 PublishOnlyToShardedPostgresqlQueues (no listeners) by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5367
* GH-5207 EF Core transactional middleware: configurable isolation level
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5369
* GH-5342 Azure Service Bus: support externally owned topics by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5368
* GH-5353 ProblemDetails factory for the 409 conflict mapping by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5370
* feat(kafka): allow setting replay group id by @Mr444-dev in
https://github.com/JasperFx/wolverine/pull/5343
* GH-5346 PostgreSQL scheduled-message poll gets the index SQL Server
has by @uniquelau in https://github.com/JasperFx/wolverine/pull/5347
* GH-5348 DurableLocalQueue.StartAsync skips an accepting queue and is
serialized by @uniquelau in
https://github.com/JasperFx/wolverine/pull/5349
* docs: circuit breakers and error policies in tests by @uniquelau in
https://github.com/JasperFx/wolverine/pull/5350
* Describe query parameters with their data annotations in OpenAPI by
@esond in https://github.com/JasperFx/wolverine/pull/5351
* [DeduplicatedWithResponse] replays ASP.NET Core IResult responses by
@esond in https://github.com/JasperFx/wolverine/pull/5352
* Merge OnException handlers for the same exception type into one catch
clause by @esond in https://github.com/JasperFx/wolverine/pull/5357
* Follow-ups: Kafka replay GroupId docs + kafka-replay --group-id
(#5306), same-type OnException docs (#5357) by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5380
* GH-5364 CloudEventsMapper keeps envelope id on re-read; stable id for
non-Guid CloudEvent ids by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5377
* GH-5361 scaffold: multi-event automation becomes one handler class by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5375
* GH-5360 scaffold: don't plan every emitted event as an Apply on every
stream by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5374
... (truncated)
Commits viewable in [compare
view](http://github.com/jasperfx/wolverine/compare/V6.61.0...V6.64.0).
</details>
Updated
[WolverineFx.RuntimeCompilation](http://github.com/jasperfx/wolverine)
from 6.61.0 to 6.64.0.
<details>
<summary>Release notes</summary>
_Sourced from [WolverineFx.RuntimeCompilation's
releases](http://github.com/jasperfx/wolverine/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
* Bump JasperFx to 2.101.0 and Weasel to 9.50.0; document the command
line under Native AOT by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5442
* Docs: the resource setup hosted service migrates message storage
regardless of AutoCreate by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5445
* GH-5443 Release lease and idempotency state for envelopes settled in
DeserializeFirst by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5448
* Bump JasperFx to 2.102.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5449
* GH-5446 Raise IWolverineObserver.CircuitBreakerReset when a
breaker-paused listener accepts again by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5451
* GH-5452: Rabbit MQ keeps one reply queue across `ResetResourceState()`
calls by @alesdvorakcz in
https://github.com/JasperFx/wolverine/pull/5453
* Bump version to 6.64.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5454
**Full Changelog**:
https://github.com/JasperFx/wolverine/compare/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
* Keep the inbox id of a durable envelope when a CloudEvent with a Guid
id is read from its data by @lahma in
https://github.com/JasperFx/wolverine/pull/5396
* GH-5395 A dead letter marked replayable mid-move is no longer deleted
without reaching the inbox by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5397
* MassTransit interop keeps the inbox id of a durable envelope when it
reads the messageId by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5398
* Default envelope ids no longer collide between processes on one
machine by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5399
* Scheduled retries on the SQL Server, MySQL, Oracle and SQLite queues
are atomic by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5408
* GH-5406 HTTP span tags are written before anything can short-circuit
the request by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5418
* GH-5416 Document waiting on a message the broker fans out to several
queues by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5419
* GH-5409 Commit the out-of-process durability chaos rig with a README
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5420
* GH-5411 A durable pop skips envelopes the inbox already holds instead
of rolling the batch back by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5421
* GH-5412 The SQL Server scheduled-message poll never waits on a lock by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5422
* GH-5413 A database queue drains a backlog without waiting a polling
interval per batch by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5424
* GH-5410 A commit that applied but reported an error is not
dead-lettered and its cascades run by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5425
* GH-5423 A node resumed after being ejected as stale does not commit
work another node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5427
* GH-5428 The MySQL expired-handled cleanup no longer locks live inbox
rows by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5431
* GH-5429 Oracle's in-transaction mark-as-handled refuses work another
node already handled by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5432
* GH-5430 SQLite in Balanced mode assigns node numbers and reads health
checks as UTC by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5433
* GH-5426 A scheduled retry on a database queue is fenced on the inbox
row's owner by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5434
* GH-5435 Tenant databases with one name on one host are told apart by
port by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5436
* GH-5438 The outbox-to-queue move is one transaction on MySQL, SQL
Server and SQLite by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5439
* Docs: schema management options for message storage, linked to Weasel
and the stateful resource model by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5437
* GH-5414 Durability chaos rig, round three by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5440
* Bump version to 6.63.0 by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5441
... (truncated)
## 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
* GH-5069 [SagaIsResponseOnly] for endpoints returning a saga as the
response by @jeremydmiller in
https://github.com/JasperFx/wolverine/pull/5366
* GH-5088 PublishOnlyToShardedPostgresqlQueues (no listeners) by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5367
* GH-5207 EF Core transactional middleware: configurable isolation level
by @jeremydmiller in https://github.com/JasperFx/wolverine/pull/5369
* GH-5342 Azure Service Bus: support externally owned topics by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5368
* GH-5353 ProblemDetails factory for the 409 conflict mapping by
@jeremydmiller in https://github.com/JasperFx/wolverine/pull/5370
* feat(kafka): allow setting replay group id by @Mr444-dev in
https://github.com/JasperFx/wolverine/pull/5343
* GH-5346 PostgreSQL scheduled-message poll gets the index SQL Server
has by @uniquelau in https://github.com/JasperFx/wolverine/pull/5347
* GH-5348 DurableLocalQueue.StartAsync skips an accepting queue and is
serialized by @uniquelau in
https://github.com/JasperFx/wolverine/pull/5349
* docs: circuit breakers and er…
This was referenced Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an optional
toProblemDetailsfactory toMapConcurrencyFailuresToConflict,MapMartenConcurrencyFailuresToConflictandMapPolecatConcurrencyFailuresToConflict. Default behavior is unchanged.The factory is stored on
WolverineHttpOptions.ConflictProblemDetailsFactory; the middlewareOnExceptionmethods takeWolverineHttpOptionsas a parameter (a DI singleton), which is how it reaches the generated code. A nullStatusis filled in as 409.Not done here: the issue's separate question about dropping the message from
Detailin the 7.0 default (#5195) is a decision for later and is not part of this change.Fixes #5353
🤖 Generated with Claude Code