Skip to content

chore: Bump Marten and 3 others#304

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Nexus.Application/multi-202761df60
Open

chore: Bump Marten and 3 others#304
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/Nexus.Application/multi-202761df60

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 4, 2026

Updated Marten from 8.37.2 to 9.5.2.

Release notes

Sourced from Marten's releases.

9.5.2

Bug fixes

  • #​4619 (#​4632) — mt_archive_stream emits explicit column lists in its INSERT…SELECT, surviving ALTER TABLE ADD COLUMN migrations that reorder the physical column layout (previously failed with 42804 after a column was added to mt_events).
  • #​4625 (#​4633) — BulkInsertEventsAsync writes mt_streams.type from the StreamAction's AggregateType, restoring UseMandatoryStreamTypeDeclaration support on the bulk path.
  • #​4641 (#​4646) — AddMartenManagedTenantsAsync no longer leaves a half-installed schema under AutoCreate.None. The admin call eagerly applies the events feature via a per-feature CreateMigrationAsync + scoped CreateOrUpdate apply, so the next append succeeds end-to-end on a virgin schema (previously failed with 42P01 / 42883).
  • #​4645 (#​4647) — DCB non-HStore tag query JOIN now includes e.tenant_id = t.tenant_id, eliminating own-event duplication under per-tenant sequences with UseTenantPartitionedEvents.

Test coverage

  • #​4617 closed — full TenantPartitionedEventsTests project (~170 tests across 50 files) covering append / read / projections / admin / DCB / async daemon / regressions under UseTenantPartitionedEvents.
  • Three projection coverage gaps closed: #​4650 (FlatTableProjection), #​4651 (DetermineActionAsync), #​4652 (doc-tables-NOT-partitioned-by-default invariant).
  • #​4649 investigated and pinned as documented intentional asymmetry — AutoCreate.CreateOnly continues to work via the lazy schema-apply path, by design (no SUT change needed).

Known follow-up — NOT in this release

  • #​4648 — AddGlobalProjection × UseTenantPartitionedEvents fails MT002 because the global event decorator writes to the *DEFAULT* tenant slot, which can't be a Postgres partition suffix. Test pin is in master asserting the throw; the underlying fix requires either routing global-aggregate events through a sibling non-partitioned table or reserving a default-tenant partition suffix. Marked as an enhancement, deferred to a later release.

🤖 Release notes assembled with Claude Code

9.5.1

What's Changed

Full Changelog: JasperFx/marten@V9.5.0...V9.5.1

9.5.0

The minor point bump here is because of some CritterWatch related features, otherwise this is all bug fixes

What's Changed

New Contributors

Full Changelog: JasperFx/marten@V9.4.0...V9.5.0

9.4.0

Marten 9.4.0

Per-tenant event partitioning and a tenant-aware async projection daemon (#​4596 / CritterWatch#​209). Built on JasperFx 2.5.0.

Highlights

  • Per-tenant event partitioning — opt in with opts.Events.UseTenantPartitionedEvents = true. On top of conjoined event tenancy, Marten partitions mt_events / mt_streams by tenant_id (native PostgreSQL LIST partitioning), gives each tenant its own event sequence (mt_events_sequence_{suffix}), and keys mt_event_progression by (name, tenant_id). Removes the single shared event store as a scalability bottleneck across tenants.
  • Tenant-aware async daemon — vectorized per-tenant high-water detection (one query per database reports the high-water position for every active tenant), per-tenant projection rebuild isolation, and cross-tenant rebuild fan-out.
  • Composite single-pass rebuild executor — read-once / fan-out rebuild for composite projections, with progression keyed on the composite's single {Name}:All shard.

Constraints for per-tenant partitioning

Validated at DocumentStore construction:

  • Requires Events.TenancyStyle = TenancyStyle.Conjoined.
  • Requires a quick append mode (EventAppendMode.Quick / QuickWithServerTimestamps); EventAppendMode.Rich is out of scope.
  • Cannot currently be combined with Events.UseArchivedStreamPartitioning (sub-partitioning by both tenant_id and is_archived is a planned follow-up).

The flag defaults to false; existing stores keep the global append path byte-for-byte.

Dependencies

  • Consumes the released JasperFx 2.5.0 packages (per-tenant partitioning surface, tenant-aware daemon abstractions, composite rebuild executor, and the SubscriptionAgent optimized-rebuild double-load fix).

Documentation

9.3.5

What's Changed

Full Changelog: JasperFx/marten@V9.3.4...V9.3.5

9.3.4

What's Changed

New Contributors

Full Changelog: JasperFx/marten@V9.3.3...V9.3.4

9.3.3

What's Changed

Full Changelog: JasperFx/marten@V9.3.2...V9.3.3

9.3.2

What's Changed

Full Changelog: JasperFx/marten@V9.3.1...V9.3.2

9.3.1

Marten 9.3.1

Fix release — bumps all four JasperFx.* dependencies to 2.2.1.

Package From To
JasperFx 2.2.0 2.2.1
JasperFx.Events 2.2.0 2.2.1
JasperFx.Events.SourceGenerator 2.2.0 2.2.1
JasperFx.SourceGenerator 2.2.0 2.2.1

No Marten-side code changes — straight dependency bump (#​4585).

Full Changelog: JasperFx/marten@V9.3.0...V9.3.1

9.3.0

Marten 9.3.0

The big-ticket items in this release are binary event serialization (#​4515) and the PostGIS + pgvector companion packages lifted into the Marten repo from CritterWatch.

Major

  • Binary event serialization for the event store (#​4515 — landed across #​4578, #​4581, #​4583, #​4584). Opt individual event types into a binary wire format (MemoryPack out of the box, or any IEventBinarySerializer you bring) on a per-event-type basis. JSON-serialized and binary-serialized events coexist in the same mt_events table so the feature can be turned on in an existing system with no migration of existing data. Works on every EventAppendMode (Rich + Quick + QuickWithServerTimestamps) and through BulkEventAppender. New optional NuGet: Marten.MemoryPack. See the binary-serialization docs for the design, registration, and the versioned-event-types schema-evolution recommendation.

  • PostGIS + pgvector companion packages (#​4576). Two new optional NuGets imported from CritterWatch:

    • Marten.PostGIS — UsePostGIS() opt-in that enables the postgis extension on every database Marten manages (multi-tenant aware), wires NetTopologySuite + GeoJSON serialization, and exposes four spatial query helpers (NearestToAsync, WithinDistanceAsync, ContainingAsync, IntersectingAsync). See the PostGIS docs.
    • Marten.PgVector — UsePgVector() opt-in that enables the vector extension on every database (also addresses #​2515 — extensions in tenant databases). VectorSearchAsync for similarity search plus an embedding-aware VectorProjection base class. See the pgvector docs.

Fixes

  • #​4575: CreatedAt.MapTo() regression in v9 (#​4577). The closed-shape storage rewrite ported every other metadata-column read-back but missed mt_created_at; this restores the v8 behavior where a [CreatedAt]-annotated / m.CreatedAt.MapTo(...)-mapped member is populated after a load.

Build / Release

  • Pack target updated (#​4582). Marten.PostGIS, Marten.PgVector, and Marten.MemoryPack are now included in the Nuke Pack target — without this they would silently never reach NuGet. 9 packages ship in 9.3.0 (up from 6): Marten, Marten.Newtonsoft, Marten.NodaTime, Marten.AspNetCore, Marten.EntityFrameworkCore, Marten.SourceGenerator, Marten.PostGIS, Marten.PgVector, Marten.MemoryPack.

  • Weasel 9.0.2 dependency bump (JasperFx/weasel#​299). Fixes PostgresqlMigrator.executeWithConcurrencyRetryAsync to reopen a Closed/Broken connection between retry attempts — eliminates the intermittent Connection is not open failure surfaced under concurrent migration races.

Documentation updates

Pages added or updated in 9.3.0:

Local docker

The local docker-compose.yml (from #​4576) layers postgresql-17-postgis-3 + postgresql-17-pgvector on the official multi-arch postgres:17 image so the Marten test suite can exercise the new extensions locally. PLv8 was dropped — Marten core SQL no longer requires it.

Full Changelog: JasperFx/marten@V9.2.1...V9.3.0

9.2.1

What's Changed

Full Changelog: JasperFx/marten@V9.2.0...V9.2.1

9.2.0

Marten 9.2.0

Features & changes

  • Override IEventStore.AllDatabases() on DocumentStore (#​4570, #​4571). Implements the store-agnostic database accessor added to JasperFx.Events.IEventStore. Delegates straight to ITenancy (mirroring IMartenStorage.AllDatabases()) and projects to IEventDatabase, so store-neutral monitoring/tooling can reach every database to call the read abstractions (AllProjectionProgress, FetchDeadLetterCountsAsync / CountDeadLetterEventsAsync) even when only IEventStore is registered in DI.

Dependencies

  • Upgraded all JasperFx.* packages to 2.2.0 (JasperFx, JasperFx.Events, JasperFx.Events.SourceGenerator, JasperFx.SourceGenerator).

Full Changelog: JasperFx/marten@V9.0.2...V9.2.0

9.0.2

Marten 9.0.2

A patch release that fixes #​4557 — self-aggregating projections failing for consumers that reference only the Marten package.

Fixes

  • #​4557 — Self-aggregating projections now work out of the box. Marten 9 dispatches conventional Apply/Create/ShouldDelete projection methods through the compile-time JasperFx.Events.SourceGenerator and has no runtime fallback, but the generator shipped as a DevelopmentDependency and never flowed to a consumer that only referenced the Marten package — surfacing as InvalidProjectionException: No source-generated dispatcher found ... at DocumentStore.For(...). Marten now bundles the analyzer in its own NuGet package, so a plain <PackageReference Include="Marten" /> runs the generator automatically. (#​4558)

  • Self-aggregating record aggregates work without a Snapshot<T> call site and without partial. Bumped JasperFx.Events / JasperFx.Events.SourceGenerator to 2.1.1 (JasperFx/jasperfx#​367): the generator now emits a self-aggregating evolver for a record from its own declaration (parity with classes), which also fixes the cross-assembly case where the aggregate type is defined in a different assembly than its registration.

  • Docs. Corrected the migration guide's projection section, which incorrectly stated Marten falls back to a runtime evolver lookup for non-partial convention projections; documented that self-aggregating Snapshot<T> types do not need to be partial (only projection subclasses do).

Dependency bumps

  • JasperFx.Events 2.1.0 → 2.1.1
  • JasperFx.Events.SourceGenerator 2.1.0 → 2.1.1

No public API changes from 9.0.1.

9.0.1

Marten 9.0.1

A patch release on the Critter Stack 2026 foundation, rolling up the latest JasperFx 2.0.1 / JasperFx.Events 2.1.0 / Weasel 9.0.1 dependencies along with several source-generator and reliability fixes.

Foundation bumps

  • JasperFx 2.0.0 → 2.0.1
  • JasperFx.Events / JasperFx.Events.SourceGenerator → 2.1.0
  • JasperFx.SourceGeneration → JasperFx.SourceGenerator 2.0.1 (package renamed; #​4555)
  • Weasel.Postgresql / Weasel.EntityFrameworkCore 9.0.0 → 9.0.1

Fixes

  • Self-aggregating source-generator fixes (via JasperFx.Events 2.1.0, consumed in #​4547):
    • #​4542 — required members on self-aggregating snapshot types no longer break generated evolver construction; default! is emitted only when a public parameterless constructor exists, otherwise RuntimeHelpers.GetUninitializedObject is used.
    • #​4543 — nullable [ReadAggregate] aggregate parameters generate correctly.
  • #​4546 — IEventDatabase dead-letter count reads (CountDeadLetterEventsAsync / FetchDeadLetterCountsAsync) are implemented on MartenDatabase via LINQ over the DeadLetterEvent document.
  • #​4540 — opt-in System.Text.Json source-generation context support (SystemTextJsonSerializer.UseTypeInfoResolver) for AOT/trimming-friendly metadata.
  • #​4552 — intermittent CI flakes fixed: feature_flag_positive advisory-lock contention (distinct ApplyChangesLockId, #​4553) and the conjoined multi-tenant query_before_saving XX000: tuple concurrently updated migration-DDL race (resolved upstream in Weasel 9.0.1 / weasel#​293).

No public API breaking changes from 9.0.0. RestoreV8Defaults() continues to revert the 9.0 default flips.

9.0.0

Marten 9.0.0 — Critter Stack 2026

The headline release of the Critter Stack 2026 wave, on the final JasperFx 2.0 + Weasel 9.0 foundation.

Highlights

  • Foundation: JasperFx 2.0.0 / JasperFx.Events 2.0.0 / Weasel 9.0.0 (final). Targets net9.0;net10.0.
  • No runtime code generation. Roslyn is gone — JasperFx.RuntimeCompiler is no longer a dependency. Document/event storage is hand-written closed-shape; compiled queries use Marten.SourceGenerator. No codegen write step for Marten.
  • Cold-start + AOT: AOT-publishable in Static mode; lazy document-mapping materialization; per-query handler-factory caching.
  • Dedupe pillar (jasperfx#​214): IStorageOperation rebased on Weasel.Core; async-daemon distributor concretes consumed from JasperFx.Events.Daemon; OperationRole / BulkInsertMode relocated to Weasel.Core.
  • Defaults flipped to best-perf: QuickWithServerTimestamps append mode, advanced async tracking, bigint events, lightweight default sessions, System.Text.Json default — all revertable via RestoreV8Defaults().
  • Versioning: IRevisioned.Version stays int (V8-compatible); new ILongVersioned (long) for MultiStreamProjection documents.
  • DCB: optional HSTORE tag storage; FetchForWritingByTags<T> for identity-less boundary aggregates.

See the migration guide (docs/migration-guide.md). Master plan: marten#​4349. Ships in lockstep with Polecat 4.0.

Commits viewable in compare view.

Updated WolverineFx.Http from 5.39.3 to 6.4.3.

Release notes

Sourced from WolverineFx.Http's releases.

6.4.1

Just hardening Wolverine against a condition that only happens (we think) in CritterWatch

What's Changed

Full Changelog: JasperFx/wolverine@V6.4.0...V6.4.1

6.4.0

This release was 100% about CritterWatch and does not impact any other functionality

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.2...V6.4.0

6.3.2

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.0...V6.3.2

6.3.0

The top line change here was a lot of work to make Wolverine able to pre-generate code as F# in addition to the existing C# model.

What's Changed

Full Changelog: JasperFx/wolverine@V6.2.2...V6.3.0

6.2.2

Patch release on top of 6.2.1.

🐛 Bug Fixes / Codegen

#​2963 (closes #​2958): EF Core transaction middleware + post-save cascade flush

The HTTP-handler codegen path under the EF Core transaction middleware + outbox cascade (GH-536) no longer fails handler compilation. Two related codegen issues addressed in this PR:

  • CS0128 duplicate var messageContext declaration in the generated handler. Cherry-picked from #​2959, originally authored by @​kentcooper — credit preserved on commit 9df45bfde. Root cause: MessageBusSource was returning a fresh CreateMessageContextWithMaybeTenantFrame per call; once cached + always returning the concrete MessageContext, the duplicate goes away.
  • CS1061 'IMessageContext' does not contain a definition for EnqueueCascadingAsync — surfaced after the cache fix because once the source produced a concrete MessageContext Variable, the downstream CaptureCascadingMessages frame still declared its MethodCall target as typeof(IMessageContext) and emitted a bad ((IMessageContext)messageContext).EnqueueCascadingAsync(…) cast. Fixed by re-targeting CaptureCascadingMessages to the concrete MessageContext type — mirrors the existing FlushOutgoingMessages pattern. Latent in src/Wolverine/Runtime/Handlers/CaptureCascadingMessages.cs since 020e79013e (2022-09-16); the variable-cache fix is what flipped it from masked to visible.

📦 Dependency bumps

  • JasperFx + JasperFx.Events + JasperFx.Events.SourceGenerator + JasperFx.SourceGenerator 2.2.1 → 2.2.3
  • JasperFx.RuntimeCompiler unchanged (own 5.x line, stays at 5.0.0)
  • Marten / Polecat unchanged (9.2.0 / 4.2.1)

Upstream JasperFx 2.2.2 release: https://github.com/JasperFx/jasperfx/releases/tag/V2.2.2 (Fix source-created codegen variable reuse, #​392). 2.2.3 was a same-day version-bump-only re-roll.

📖 Documentation

  • #​2960 (@​outofrange-consulting): clarify the JasperFx command-line integration link in the diagnostics docs.
  • #​2964 (closes #​2962): re-align the dead-letter REST API reference with the current DeadLetterEnvelopeGetRequest / DeadLetterEnvelopeResults / DeadLetterEnvelopeIdsRequest signatures — the docs still described the pre-5 cursor-based pagination (StartId/NextId) and the legacy DeadLetterEnvelopesFoundResponse wrapper. Updated for offset-based PageNumber pagination, the multi-store IReadOnlyList<DeadLetterEnvelopeResults> response shape, and tenant-aware Ids request bodies.

🧪 Known issues

  • #​2965: SharedMemory transport does not serialize envelopes on cross-host send. Surfaces as a MartenTests.Distribution.with_ancillary_stores.spread_out_over_multiple_hosts failure where AssignAgent system commands arrive at the destination node with empty Data/MessageType and the receive pipeline can't deserialize them. Long-standing — the marten CI workflow has been red on this test through V6.2.0 and V6.2.1, predates this release line entirely. Unblocked the V6.2.2 cycle by adding [Fact(Skip = "…")] referencing #​2965; the underlying serialization bug is tracked separately and is out of scope for a JasperFx pin-bump patch release.

Full changelog: JasperFx/wolverine@V6.2.1...V6.2.2

6.2.1

Patch release picking up upstream JasperFx 2.2.1 fixes. No Wolverine code changes — pure dependency bump.

Bumped pins

Package From To
JasperFx 2.2.0 2.2.1
JasperFx.Events 2.2.0 2.2.1
JasperFx.Events.SourceGenerator 2.2.0 2.2.1
JasperFx.SourceGenerator 2.2.0 2.2.1

Unchanged

Package Version Reason
JasperFx.RuntimeCompiler 5.0.0 Own 5.x line — the Roslyn runtime-compiler package was decoupled from the JasperFx 2.x family in #​2876.
Marten family 9.2.0 Latest.
Polecat 4.2.1 Latest (bumped in 6.2.0 via #​2947).

Related links

6.2.0

Bug-fix + feature release on top of 6.1.0 — 13 PRs.

✨ New features

Custom Result<T> Support — #​2952 (refs #​2221)

First three phases of native Result<T>-style handler return-value support: ResultPolicy registry, handler-side unwrapping seams, and caller-side InvokeAsync<T> unwrap. Lays the groundwork for integrating with libraries like ErrorOr, OneOf, FluentResults, etc.

DbContext Abstractions for EF Core Transaction Middleware — #​2919, #​2954

The EF Core transaction middleware now binds correctly when handler parameters are declared as interface or abstract base abstractions over a concrete DbContext. Multiple abstractions to the same DbContext are supported in a single handler — the runtime resolves them all to the same scoped instance, and the transaction still auto-applies.

📖 DbContext Abstractions docs

🚀 Performance

Outgoing Envelope Pooling — #​2956 (closes #​2955)

MessageRouter.RouteForPublish now acquires from the runtime envelope pool (originally introduced in #​2741 for the Executor sites in 6.1.0) when the route's sender is an InlineSendingAgent or BufferedSendingAgent. Measured −504 B/op (−90 %) on the transport-bound publish/send paths in the CritterStackScalability harness, with ~10× fewer Gen0 collections per 1k ops. DurableSendingAgent, local-queue agents, and ISenderRequiresCallback senders are explicitly excluded — different lifecycle plumbing required, tracked as follow-ups.

🐛 Bug fixes

Marten / Polecat

  • #​2943 Fix scheduled-cascade loss from [ReadAggregate] / [DocumentExists] handlers (closes #​2941).
  • #​2948 Pre-populate chain.AncillaryStoreType in Phase A so the inbox-routing map sees [MartenStore] (closes #​2944).
  • #​2947 Bump Polecat 4.1.1 → 4.2.1 and unskip the three Polecat scheduled-cascade tests.

Persistence (Postgres / MySQL)

  • #​2945 Route PostgresqlQueue identifiers through Weasel's PostgresqlIdentifier.Shorten() so long queue names don't overflow Postgres's 63-byte identifier limit (closes #​2942).
  • #​2946 Emit PersistNodeRecord SQL with unquoted schema (MySQL, closes #​2940).

Pulsar

  • #​2950 Fix KeyNotFoundException acking batch messages on partitioned topics (supersedes #​2883).

Distributed agents

  • #​2951 Bump remote-node agent InvokeAsync<T> reply timeout 10 s → 30 s (closes #​2949).

Quality

  • #​2894 Dispose more resources (@​dmytro-pryvedeniuk).

📖 Documentation

  • #​2953 AOT callout for FluentValidation in the HTTP validation guide (addresses #​2910). 📖 HTTP validation docs
  • #​2954 Extended docs + scenario tests for the new EF Core DbContext abstractions (above).

📦 Dependency bumps

  • Polecat 4.1.1 → 4.2.1 (#​2947).

Full changelog: JasperFx/wolverine@V6.1.0...V6.2.0
... (truncated)

6.1.0

Wolverine 6.1.0

Minor release. Critter Stack dependency refresh, plus the rollup of the entire post-6.0.0 6.0.x line — most significantly the AOT runtime-scanning-elimination work and a new command-line handler-discovery diagnostic.

ℹ️ There was no standalone 6.0.1 tag/GitHub release (it shipped as a NuGet version only), so the changelog below covers every PR merged since 6.0.0 — which includes everything released as 6.0.1 through 6.0.3.

Dependencies

  • Marten / Marten.AspNetCore / Marten.Newtonsoft: 9.0.1 → 9.2.0
  • JasperFx.* (non-RuntimeCompiler): 2.1.3 → 2.2.0 (#​2938)
  • Polecat: 4.1.1 (unchanged — already latest)
  • JasperFx.RuntimeCompiler: 5.0.0 (unchanged — own 5.x line)

Marten 9.2.0 now bundles JasperFx.Events.SourceGenerator as an analyzer, so projects referencing Wolverine.Marten receive it transitively. The previously-explicit analyzer references were dropped from the 8 Marten-referencing projects to avoid running the generator twice, which produced duplicate Evolve/*Evolver build errors (#​2939). PolecatTests retains its explicit reference because Polecat does not bundle the generator.

New & Noteworthy

AOT: eliminate runtime assembly scanning — AOT Publishing. Static-mode apps no longer scan assemblies at startup; discovery now flows through source-generated manifests:

  • Handlers + message types — #​2906 / #​2928
  • HTTP endpoints — #​2925 / #​2929
  • gRPC services (incl. the direct-mapped mode) — #​2926 / #​2930 / #​2934
  • [WolverineHandlerModule] assemblies, with no filesystem probe — #​2905 / #​2935
  • Extension discovery manifest — #​2902 / #​2918
  • Remaining ad-hoc discovery scans routed through JasperFx TypeQuery — #​2909 / #​2932
  • Generated HTTP/gRPC types attached by full name instead of a GetTypes() scan — #​2908 / #​2936

Command-line handler-discovery diagnostic — Command Line Integration · Command Line Diagnostics tutorial. New dotnet run -- wolverine-diagnostics describe-handlers <Type> runs DescribeHandlerMatch from the CLI so you can troubleshoot handler discovery without editing your bootstrapping code — #​2921 / #​2923

Build-time OpenAPI generation — Command Line Integration. dotnet run -- openapi generates the OpenAPI document without starting the host (no database/broker required) — #​2903 / #​2911

SQS fair queues on standard queues — support MessageGroupId on standard Amazon SQS queues — #​2886 / #​2889

SignalR ClaimsPrincipal — the connection's ClaimsPrincipal is now exposed on SignalREnvelope — #​2927 / #​2937

EF Core transactional outbox timing fix — the EF Core transaction and outbox flush now complete before the HTTP response is written — #​2917 / #​2920

Mixed-lifetime IEnumerable<T> support; Lamar removed — handlers depending on a mixed singleton/scoped IEnumerable<T> now resolve every element correctly; Lamar is no longer used or supported, and the built-in ServiceProvider is the container — #​2896 / #​2914

Aggregate handler naming clarity — clarified and guarded the *AggregateHandler naming convention vs. [ReadAggregate] — #​2924

Production code-generation guidance — Code Generation. How to drop Roslyn from production images, with a linked CqrsMinimalApi sample — #​2900 / #​2912

Bug fixes

  • Ancillary store outbox schema for projection side effects — #​2887 / #​2888
  • NRE from null-Sender routes built during description mode — #​2897 / #​2899

What's Changed

6.0.0

Wolverine 6.0.0 — Critter Stack 2026

The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).

Highlights

  • Foundation (final): JasperFx 2.0.0 / JasperFx.RuntimeCompiler 5.0.0 / Marten 9.0.0 / Polecat 4.0.0 / Weasel 9.0.0. Targets net9.0;net10.0.
  • Runtime codegen decoupled from core (BREAKING): WolverineFx no longer ships Roslyn. Apps in the default TypeLoadMode.Dynamic must add WolverineFx.RuntimeCompilation, or pre-generate via codegen write + TypeLoadMode.Static (the trimmer then drops Roslyn). See the migration guide.
  • ServiceLocationPolicy.NotAllowed is the default (BREAKING) — restructure registrations, allow-list per type, or call opts.RestoreV5Defaults() to revert.
  • AOT-clean (pillar #​213): every packaged library carries IsAotCompatible=true (except the intentional WolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.
  • Cold-start (pillar #​212): Tier-1 pre-generated static handler registry skips handler-discovery scanning in Static mode.
  • Newtonsoft extracted to WolverineFx.Newtonsoft / WolverineFx.Http.Newtonsoft; IForwardsTo<T> discovery now explicit; removed [Obsolete] APIs (EventForwardingToWolverine, RedisTransport.BuildRedisStreamUri, PulsarEndpoint.UriFor).

Migration guide: https://wolverinefx.net/guide/migration.html (or docs/guide/migration.md). Master plan: wolverine#​2715. Remaining release-cut comms items tracked in #​2745.

Commits viewable in compare view.

Updated WolverineFx.Http.Marten from 5.39.3 to 6.4.3.

Release notes

Sourced from WolverineFx.Http.Marten's releases.

6.4.1

Just hardening Wolverine against a condition that only happens (we think) in CritterWatch

What's Changed

Full Changelog: JasperFx/wolverine@V6.4.0...V6.4.1

6.4.0

This release was 100% about CritterWatch and does not impact any other functionality

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.2...V6.4.0

6.3.2

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.0...V6.3.2

6.3.0

The top line change here was a lot of work to make Wolverine able to pre-generate code as F# in addition to the existing C# model.

What's Changed

Full Changelog: JasperFx/wolverine@V6.2.2...V6.3.0

6.2.2

Patch release on top of 6.2.1.

🐛 Bug Fixes / Codegen

#​2963 (closes #​2958): EF Core transaction middleware + post-save cascade flush

The HTTP-handler codegen path under the EF Core transaction middleware + outbox cascade (GH-536) no longer fails handler compilation. Two related codegen issues addressed in this PR:

  • CS0128 duplicate var messageContext declaration in the generated handler. Cherry-picked from #​2959, originally authored by @​kentcooper — credit preserved on commit 9df45bfde. Root cause: MessageBusSource was returning a fresh CreateMessageContextWithMaybeTenantFrame per call; once cached + always returning the concrete MessageContext, the duplicate goes away.
  • CS1061 'IMessageContext' does not contain a definition for EnqueueCascadingAsync — surfaced after the cache fix because once the source produced a concrete MessageContext Variable, the downstream CaptureCascadingMessages frame still declared its MethodCall target as typeof(IMessageContext) and emitted a bad ((IMessageContext)messageContext).EnqueueCascadingAsync(…) cast. Fixed by re-targeting CaptureCascadingMessages to the concrete MessageContext type — mirrors the existing FlushOutgoingMessages pattern. Latent in src/Wolverine/Runtime/Handlers/CaptureCascadingMessages.cs since 020e79013e (2022-09-16); the variable-cache fix is what flipped it from masked to visible.

📦 Dependency bumps

  • JasperFx + JasperFx.Events + JasperFx.Events.SourceGenerator + JasperFx.SourceGenerator 2.2.1 → 2.2.3
  • JasperFx.RuntimeCompiler unchanged (own 5.x line, stays at 5.0.0)
  • Marten / Polecat unchanged (9.2.0 / 4.2.1)

Upstream JasperFx 2.2.2 release: https://github.com/JasperFx/jasperfx/releases/tag/V2.2.2 (Fix source-created codegen variable reuse, #​392). 2.2.3 was a same-day version-bump-only re-roll.

📖 Documentation

  • #​2960 (@​outofrange-consulting): clarify the JasperFx command-line integration link in the diagnostics docs.
  • #​2964 (closes #​2962): re-align the dead-letter REST API reference with the current DeadLetterEnvelopeGetRequest / DeadLetterEnvelopeResults / DeadLetterEnvelopeIdsRequest signatures — the docs still described the pre-5 cursor-based pagination (StartId/NextId) and the legacy DeadLetterEnvelopesFoundResponse wrapper. Updated for offset-based PageNumber pagination, the multi-store IReadOnlyList<DeadLetterEnvelopeResults> response shape, and tenant-aware Ids request bodies.

🧪 Known issues

  • #​2965: SharedMemory transport does not serialize envelopes on cross-host send. Surfaces as a MartenTests.Distribution.with_ancillary_stores.spread_out_over_multiple_hosts failure where AssignAgent system commands arrive at the destination node with empty Data/MessageType and the receive pipeline can't deserialize them. Long-standing — the marten CI workflow has been red on this test through V6.2.0 and V6.2.1, predates this release line entirely. Unblocked the V6.2.2 cycle by adding [Fact(Skip = "…")] referencing #​2965; the underlying serialization bug is tracked separately and is out of scope for a JasperFx pin-bump patch release.

Full changelog: JasperFx/wolverine@V6.2.1...V6.2.2

6.2.1

Patch release picking up upstream JasperFx 2.2.1 fixes. No Wolverine code changes — pure dependency bump.

Bumped pins

Package From To
JasperFx 2.2.0 2.2.1
JasperFx.Events 2.2.0 2.2.1
JasperFx.Events.SourceGenerator 2.2.0 2.2.1
JasperFx.SourceGenerator 2.2.0 2.2.1

Unchanged

Package Version Reason
JasperFx.RuntimeCompiler 5.0.0 Own 5.x line — the Roslyn runtime-compiler package was decoupled from the JasperFx 2.x family in #​2876.
Marten family 9.2.0 Latest.
Polecat 4.2.1 Latest (bumped in 6.2.0 via #​2947).

Related links

6.2.0

Bug-fix + feature release on top of 6.1.0 — 13 PRs.

✨ New features

Custom Result<T> Support — #​2952 (refs #​2221)

First three phases of native Result<T>-style handler return-value support: ResultPolicy registry, handler-side unwrapping seams, and caller-side InvokeAsync<T> unwrap. Lays the groundwork for integrating with libraries like ErrorOr, OneOf, FluentResults, etc.

DbContext Abstractions for EF Core Transaction Middleware — #​2919, #​2954

The EF Core transaction middleware now binds correctly when handler parameters are declared as interface or abstract base abstractions over a concrete DbContext. Multiple abstractions to the same DbContext are supported in a single handler — the runtime resolves them all to the same scoped instance, and the transaction still auto-applies.

📖 DbContext Abstractions docs

🚀 Performance

Outgoing Envelope Pooling — #​2956 (closes #​2955)

MessageRouter.RouteForPublish now acquires from the runtime envelope pool (originally introduced in #​2741 for the Executor sites in 6.1.0) when the route's sender is an InlineSendingAgent or BufferedSendingAgent. Measured −504 B/op (−90 %) on the transport-bound publish/send paths in the CritterStackScalability harness, with ~10× fewer Gen0 collections per 1k ops. DurableSendingAgent, local-queue agents, and ISenderRequiresCallback senders are explicitly excluded — different lifecycle plumbing required, tracked as follow-ups.

🐛 Bug fixes

Marten / Polecat

  • #​2943 Fix scheduled-cascade loss from [ReadAggregate] / [DocumentExists] handlers (closes #​2941).
  • #​2948 Pre-populate chain.AncillaryStoreType in Phase A so the inbox-routing map sees [MartenStore] (closes #​2944).
  • #​2947 Bump Polecat 4.1.1 → 4.2.1 and unskip the three Polecat scheduled-cascade tests.

Persistence (Postgres / MySQL)

  • #​2945 Route PostgresqlQueue identifiers through Weasel's PostgresqlIdentifier.Shorten() so long queue names don't overflow Postgres's 63-byte identifier limit (closes #​2942).
  • #​2946 Emit PersistNodeRecord SQL with unquoted schema (MySQL, closes #​2940).

Pulsar

  • #​2950 Fix KeyNotFoundException acking batch messages on partitioned topics (supersedes #​2883).

Distributed agents

  • #​2951 Bump remote-node agent InvokeAsync<T> reply timeout 10 s → 30 s (closes #​2949).

Quality

  • #​2894 Dispose more resources (@​dmytro-pryvedeniuk).

📖 Documentation

  • #​2953 AOT callout for FluentValidation in the HTTP validation guide (addresses #​2910). 📖 HTTP validation docs
  • #​2954 Extended docs + scenario tests for the new EF Core DbContext abstractions (above).

📦 Dependency bumps

  • Polecat 4.1.1 → 4.2.1 (#​2947).

Full changelog: JasperFx/wolverine@V6.1.0...V6.2.0
... (truncated)

6.1.0

Wolverine 6.1.0

Minor release. Critter Stack dependency refresh, plus the rollup of the entire post-6.0.0 6.0.x line — most significantly the AOT runtime-scanning-elimination work and a new command-line handler-discovery diagnostic.

ℹ️ There was no standalone 6.0.1 tag/GitHub release (it shipped as a NuGet version only), so the changelog below covers every PR merged since 6.0.0 — which includes everything released as 6.0.1 through 6.0.3.

Dependencies

  • Marten / Marten.AspNetCore / Marten.Newtonsoft: 9.0.1 → 9.2.0
  • JasperFx.* (non-RuntimeCompiler): 2.1.3 → 2.2.0 (#​2938)
  • Polecat: 4.1.1 (unchanged — already latest)
  • JasperFx.RuntimeCompiler: 5.0.0 (unchanged — own 5.x line)

Marten 9.2.0 now bundles JasperFx.Events.SourceGenerator as an analyzer, so projects referencing Wolverine.Marten receive it transitively. The previously-explicit analyzer references were dropped from the 8 Marten-referencing projects to avoid running the generator twice, which produced duplicate Evolve/*Evolver build errors (#​2939). PolecatTests retains its explicit reference because Polecat does not bundle the generator.

New & Noteworthy

AOT: eliminate runtime assembly scanning — AOT Publishing. Static-mode apps no longer scan assemblies at startup; discovery now flows through source-generated manifests:

  • Handlers + message types — #​2906 / #​2928
  • HTTP endpoints — #​2925 / #​2929
  • gRPC services (incl. the direct-mapped mode) — #​2926 / #​2930 / #​2934
  • [WolverineHandlerModule] assemblies, with no filesystem probe — #​2905 / #​2935
  • Extension discovery manifest — #​2902 / #​2918
  • Remaining ad-hoc discovery scans routed through JasperFx TypeQuery — #​2909 / #​2932
  • Generated HTTP/gRPC types attached by full name instead of a GetTypes() scan — #​2908 / #​2936

Command-line handler-discovery diagnostic — Command Line Integration · Command Line Diagnostics tutorial. New dotnet run -- wolverine-diagnostics describe-handlers <Type> runs DescribeHandlerMatch from the CLI so you can troubleshoot handler discovery without editing your bootstrapping code — #​2921 / #​2923

Build-time OpenAPI generation — Command Line Integration. dotnet run -- openapi generates the OpenAPI document without starting the host (no database/broker required) — #​2903 / #​2911

SQS fair queues on standard queues — support MessageGroupId on standard Amazon SQS queues — #​2886 / #​2889

SignalR ClaimsPrincipal — the connection's ClaimsPrincipal is now exposed on SignalREnvelope — #​2927 / #​2937

EF Core transactional outbox timing fix — the EF Core transaction and outbox flush now complete before the HTTP response is written — #​2917 / #​2920

Mixed-lifetime IEnumerable<T> support; Lamar removed — handlers depending on a mixed singleton/scoped IEnumerable<T> now resolve every element correctly; Lamar is no longer used or supported, and the built-in ServiceProvider is the container — #​2896 / #​2914

Aggregate handler naming clarity — clarified and guarded the *AggregateHandler naming convention vs. [ReadAggregate] — #​2924

Production code-generation guidance — Code Generation. How to drop Roslyn from production images, with a linked CqrsMinimalApi sample — #​2900 / #​2912

Bug fixes

  • Ancillary store outbox schema for projection side effects — #​2887 / #​2888
  • NRE from null-Sender routes built during description mode — #​2897 / #​2899

What's Changed

6.0.0

Wolverine 6.0.0 — Critter Stack 2026

The messaging/orchestration release completing the Critter Stack 2026 wave, on the final foundation (JasperFx 2.0 / Weasel 9.0 / Marten 9.0 / Polecat 4.0).

Highlights

  • Foundation (final): JasperFx 2.0.0 / JasperFx.RuntimeCompiler 5.0.0 / Marten 9.0.0 / Polecat 4.0.0 / Weasel 9.0.0. Targets net9.0;net10.0.
  • Runtime codegen decoupled from core (BREAKING): WolverineFx no longer ships Roslyn. Apps in the default TypeLoadMode.Dynamic must add WolverineFx.RuntimeCompilation, or pre-generate via codegen write + TypeLoadMode.Static (the trimmer then drops Roslyn). See the migration guide.
  • ServiceLocationPolicy.NotAllowed is the default (BREAKING) — restructure registrations, allow-list per type, or call opts.RestoreV5Defaults() to revert.
  • AOT-clean (pillar #​213): every packaged library carries IsAotCompatible=true (except the intentional WolverineFx.RuntimeCompilation); Static-mode publish drops Roslyn.
  • Cold-start (pillar #​212): Tier-1 pre-generated static handler registry skips handler-discovery scanning in Static mode.
  • Newtonsoft extracted to WolverineFx.Newtonsoft / WolverineFx.Http.Newtonsoft; IForwardsTo<T> discovery now explicit; removed [Obsolete] APIs (EventForwardingToWolverine, RedisTransport.BuildRedisStreamUri, PulsarEndpoint.UriFor).

Migration guide: https://wolverinefx.net/guide/migration.html (or docs/guide/migration.md). Master plan: wolverine#​2715. Remaining release-cut comms items tracked in #​2745.

Commits viewable in compare view.

Updated WolverineFx.Marten from 5.39.3 to 6.4.3.

Release notes

Sourced from WolverineFx.Marten's releases.

6.4.1

Just hardening Wolverine against a condition that only happens (we think) in CritterWatch

What's Changed

Full Changelog: JasperFx/wolverine@V6.4.0...V6.4.1

6.4.0

This release was 100% about CritterWatch and does not impact any other functionality

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.2...V6.4.0

6.3.2

What's Changed

Full Changelog: JasperFx/wolverine@V6.3.0...V6.3.2

6.3.0

The top line change here was a lot of work to make Wolverine able to pre-generate code as F# in addition to the existing C# model.

What's Changed

Full Changelog: JasperFx/wolverine@V6.2.2...V6.3.0

6.2.2

Patch release on top of 6.2.1.

🐛 Bug Fixes / Codegen

#​2963 (closes #​2958): EF Core transaction middleware + post-save cascade flush

The HTTP-handler codegen path under the EF Core transaction middleware + outbox cascade (GH-536) no longer fails handler compilation. Two related codegen issues addressed in this PR:

  • CS0128 duplicate var messageContext declaration in the generated handler. Cherry-picked from #​2959, originally authored by @​kentcooper — credit preserved on commit 9df45bfde. Root cause: MessageBusSource was returning a fresh CreateMessageContextWithMaybeTenantFrame per call; once cached + always returning the concrete MessageContext, the duplicate goes away.
  • CS1061 'IMessageContext' does not contain a definition for EnqueueCascadingAsync — surfaced after the cache fix because once the source produced a concrete MessageContext Variable, the downstream CaptureCascadingMessages frame still declared its MethodCall target as typeof(IMessageContext) and emitted a bad ((IMessageContext)messageContext).EnqueueCascadingAsync(…) cast. Fixed by re-targeting CaptureCascadingMessages to the concrete MessageContext type — mirrors the existing FlushOutgoingMessages pattern. Latent in src/Wolverine/Runtime/Handlers/CaptureCascadingMessages.cs since 020e79013e (2022-09-16); the variable-cache fix is what flipped it from masked to visible.

📦 Dependency bumps

  • JasperFx + JasperFx.Events + JasperFx.Events.SourceGenerator + JasperFx.SourceGenerator 2.2.1 → 2.2.3
  • JasperFx.RuntimeCompiler unchanged (own 5.x line, stays at 5.0.0)
  • Marten / Polecat unchanged (9.2.0 / 4.2.1)

Upstream JasperFx 2.2.2 release: https://github.com/JasperFx/jasperfx/releases/tag/V2.2.2 (Fix source-created codegen variable reuse, #​392). 2.2.3 was a same-day version-bump-only re-roll.

📖 Documentation

  • #​2960 (@​outofrange-consulting): clarify the JasperFx command-line integration link in the diagnostics docs.
  • #​2964 (closes #​2962): re-align the dead-letter REST API reference with the current DeadLetterEnvelopeGetRequest / DeadLetterEnvelopeResults / DeadLetterEnvelopeIdsRequest signatures — the docs still described the pre-5 cursor-based pagination (StartId/NextId) and the legacy DeadLetterEnvelopesFoundResponse wrapper. Updated for offset-based PageNumber pagination, the multi-store IReadOnlyList<DeadLetterEnvelopeResults> response shape, and tenant-aware Ids request bodies.

🧪 Known issues

  • #​2965: SharedMemory transport does not serialize envelopes on cross-host send. Surfaces as a MartenTests.Distribution.with_ancillary_stores.spread_out_over_multiple_hosts failure where AssignAgent sys...

_Description has bee...

Description has been truncated

@dependabot
chore: Bump Marten and 3 others
7fc3767 
Bumps Marten from 8.37.2 to 9.5.2
Bumps WolverineFx.Http from 5.39.3 to 6.4.3
Bumps WolverineFx.Http.Marten from 5.39.3 to 6.4.3
Bumps WolverineFx.Marten from 5.39.3 to 6.4.3

---
updated-dependencies:
- dependency-name: Marten
  dependency-version: 9.5.2
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: WolverineFx.Http
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: WolverineFx.Http.Marten
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: WolverineFx.Marten
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: WolverineFx.Http
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: WolverineFx.Http.Marten
  dependency-version: 6.4.3
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot mentioned this pull request Jun 4, 2026
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies dotnet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

No source-generated dispatcher found for Marten.Events.Aggregation.SingleStreamProjection<MyType, System.Guid>

0 participants