NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
NuGet
NuGet, #1326 most downloaded on NuGet
Foundational helpers and command line support used by JasperFx and the Critter Stack projects
Latest stable
2.102.0
Last release 13 days ago
09 Nov 2026
Ships on a steady schedule
a new release about every 8 days
Most releases are documented
notes for 52 of the last 60 stable releases
3 versions withdrawn
withdrawn after publishing
127 years old
276 releases · first in 1900
Drag across the ruler to compare, or tap a release to open it.
JasperFx 2.102.0 is a minor release with one new IEventDatabase capability. It lets monitoring report projection lag as time rather than as a count of
JasperFx 2.102.0 is a minor release with one new IEventDatabase capability. It lets monitoring report projection lag as time rather than as a count of events.
IEventDatabase.FetchFirstEventTimestampsAfterAsync, the age of the oldest unprocessed event (#1150 / #1151).
(TenantId, Sequence) position, it returns the store's timestamp of the first event with a higher sequence, or null when there is none (the shard is caught up). You get one PendingEventAge(TenantId, Sequence, Timestamp) per position, in the order asked. PendingEventAge also has IsCaughtUp and AgeAt(now), which never returns a negative age when clocks are skewed.NotSupportedException on a store that hasn't implemented it. A null timestamp means "caught up", so that default can't answer without reporting a lagging shard as current. The single-position convenience FetchFirstEventTimestampAfterAsync(sequence, tenantId) calls the batched member by default. The in-memory prototyping store implements both.PendingEventAgeCompliance suite, gated by SupportsPendingEventAges (default false), with 12 facts. They cover the "strictly after" rule, ordering and duplicates, archived events and conjoined tenant scoping. A new SupportsStreamArchiving fixture flag (default true) gates the archived facts. Stores must enroll the new suite (or excuse it) or ComplianceSuiteInventory.AssertEnrolled fails.Marten, Polecat and Fisher implement the method in their JasperFx 2.102.0 upgrades.
Full Changelog: v2.101.1...v2.102.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
JasperFx 2.101.1 is a patch release with one fix.
JasperFx 2.101.1 is a patch release with one fix.
StopAsync / PauseAsync calls on the projection coordinator no longer throw ObjectDisposedException (#1148 / #1149).
ProjectionCoordinatorBase read, awaited across, then disposed and replaced its shared cancellation source and runner with nothing serializing callers. Two stops in flight at once could cancel a source the other had just disposed. Two starts in flight at once could each build a leadership loop, leaving one running that nothing would ever cancel.RunCommand stops the host again when ApplicationStopping fires, so tests hosting an app through WebApplicationFactory or Alba had two IHost.StopAsync calls racing at teardown.ProjectionCoordinator pick this up from the base class. Marten's ExplicitProjectionCoordinator has its own fix in JasperFx/marten#5843.StressTests project that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.Full Changelog: v2.101.0...v2.101.1
JasperFx 2.101.0 makes the command line work from a Native AOT binary, adds a build warning for a source generator that never reaches the compiler, an
JasperFx 2.101.0 makes the command line work from a Native AOT binary, adds a build warning for a source generator that never reaches the compiler, and fixes assembly scanning on Windows.
help, run, describe and every other command failed from a native binary, because commands were found and built through reflection that trimming removes.JasperFx.SourceGenerator registers each command, a factory for it and its input, and an [InjectService] injector, as ordinary code the trimmer keeps. JasperFx and JasperFx.Events now ship built with it, and describe no longer throws when referenced-assembly metadata is missing.JasperFx.SourceGenerator in every assembly that contributes commands. The trimming warnings on ApplyJasperFxExtensions / RunJasperFxCommands now say when it is safe to suppress them.aot-cli CI job publishes a CreateSlimBuilder app with Native AOT and runs help, help <command>, an application command, check-env, describe and run from the binary.JFXEVT1138: a build warning when the events source generator never reaches the compiler (#1138 / #1139).
JasperFx.Events.SourceGenerator is pinned to a different version than the copy bundled by a store, the SDK keeps the higher copy, and a project target then removes that one.JasperFxEventsReportLostSourceGenerator=false.runtimes/native folders on Windows too, and skips satellite resource assemblies (#1143 / #1145).
"/runtimes" with a forward slash, so on Windows every native DLL, such as the coverage collector's covrun64.dll, was tried twice and failed on each host start.Full Changelog: v2.100.1...v2.101.0
JasperFx 2.100.1 is a patch release with one fix.
JasperFx 2.100.1 is a patch release with one fix.
CatchUpAsync no longer returns cleanly while a shard has faulted (#1134 / #1135). The tracker delivers a failed shard's state to listeners asynchronously, so the daemon's Recorder could still be empty when CatchUpAsync checked it, and it reported success though a projection had thrown. That was the cause of flaky daemon tests in Marten (marten#5696) and Polecat (polecat#933). ForceAllMartenDaemonActivityToCatchUpAsync and its Polecat and Fisher equivalents now fail when a projection throws.Full Changelog: v2.100.0...v2.100.1
JasperFx 2.100.0 is mostly about running many tenants in one process: per-tenant projection work can be queued and bounded, and store-wide rebuilds fa
JasperFx 2.100.0 is mostly about running many tenants in one process: per-tenant projection work can be queued and bounded, and store-wide rebuilds fan out per tenant.
DaemonSettings.SerializeTenantProjectionBatches, #1127).GenerationRules.ReuseCompiledAssemblies, #1114 / #1129), and AssemblyGenerator's reference cache is keyed on path plus last-write time (#1110 / #1126).ComplianceSuiteInventory, so a store can't leave a suite out silently (#1123).StartsStream/Against, a second StartsStream<T>() throws instead of silently replacing the first, and a derived snapshot view is placed in its aggregate's chapter. The projection stepper also assigns the document's identity.Full Changelog: v2.99.0...v2.100.0
EntityDescriptor.Ddl: the CREATE script for an EF Core entity's table by @jeremydmiller in #1109
Full Changelog: V2.98.0...v2.99.0
Full Changelog: https://github.com/JasperFx/jasperfx/compare/V2.98.0...v2.99.0
JasperFx 2.98.0 covers everything since 2.97.0. 2.97.1 was tagged in the source but never reached NuGet, so its fixes ship here.
JasperFx 2.98.0 covers everything since 2.97.0. 2.97.1 was tagged in the source but never reached NuGet, so its fixes ship here.
Side effects keep their correlation id (#1101, #1105). With event metadata on, a message published with slice.PublishMessage(message) now carries the correlation id that all of the slice's appended events agree on, on the async path and both inline paths. It used to get the daemon page's id, which merged unrelated flows that landed in one page, or a fresh id inline. This changes the envelope's correlation id for existing side effects. Where the events don't agree, or event metadata is off, nothing changes. Causation is deliberately left out, so a side effect's handler still names that side effect as the cause of what it appends.
An HTTP endpoint and a message handler fold cleanly (#1099, #1103). Two derived sources claiming Http and MessageHandler on one slice no longer raise three SourceDisagreement hotspots. TriggerKind, HandlerType, HandlerMethod and Origin keep the HTTP side in either source order. Other real disagreements still raise their hotspots.
Cloned events keep their correlation and causation ids (#1107). Fan-out and ReplaceEvent used to drop them.
SubscriptionDescriptor.PublishedTypes says what a projection writes, including event projections and composites, where AggregateType is null. Empty doesn't mean "writes nothing": a flat table projection has rows with no type. IPublishesTypes is the new non-generic interface behind it (#1102, #1106).MessageMetadata.From(IEvent) attributes a side effect to one event when a slice spans several flows (#1105).EventModelSliceDescriptor.AdditionalEntryPoints and EventModelEntryPoint keep the message handler beside the endpoint on a folded slice. Every slice's JSON now carries additionalEntryPoints: [], and older payloads read as empty (#1103).IsValidNumber no longer accepts text that isn't a number, and ReadExpectedBufferAsync fails on a short read (#1098).TryCreateUsage lists its projections (#1106).EventProjectionRegistrationCompliance facts need no store changes. They pass on Marten, Polecat and Fisher.BatchingChannel.TriggerBatch covers items posted before it by @jeremydmiller in #1096
Full Changelog: V2.96.2...v2.97.0
Full Changelog: https://github.com/JasperFx/jasperfx/compare/V2.96.2...v2.97.0
RunCommand now awaits host shutdown instead of blocking a thread-pool thread with ManualResetEventSlim.Wait() . That block could starve the thread poo
Source generator: keep a required member's initializer when constructing a missing aggregate by @kenkendk in #1088
Full Changelog: V2.96.0...v2.96.1
Full Changelog: https://github.com/JasperFx/jasperfx/compare/V2.96.0...v2.96.1
An Observed vs Derived Origin no longer raises a SourceDisagreement : an observed origin names the service the slice was watched on, not a store, so r
Origin no longer raises a SourceDisagreement: an observed origin names the service the slice was watched on, not a store, so runtime observation confirms the slice. Two observed services or two derived stores still disagree (#1083, #1085).SourceDisagreement renders as a muted "≠" badge on the disputed card (or the slice header for roles with no card) instead of a red sticky; findings keep their stickies. disagreementPresentation="sticky" restores the old rendering, and placeDisagreements / disagreementLines are exported for host legends and selection detail (#1084, #1085).Full Changelog : V2.95.0...V2.95.1
Full Changelog: V2.95.0...V2.95.1
Full Changelog: https://github.com/JasperFx/jasperfx/compare/V2.95.0...V2.95.1
Full Changelog : V2.94.0...V2.95.0
Full Changelog: V2.94.0...V2.95.0
Full Changelog: https://github.com/JasperFx/jasperfx/compare/V2.94.0...V2.95.0
DocumentTypeRef.IsSoftDeleted: a console can tell before a delete whether it is permanent
All three are binary-compatible additions; default implementations throw NotSupportedException naming a store built against an older JasperFx. PR #1074.
Nothing published for this version
Projection start floors ( #809 , #1068 ): a rebuild now honours a configured SubscribeFromSequence / SubscribeFromTime floor and seeds the progression
SubscribeFromSequence / SubscribeFromTime floor and seeds the progression row first (it used to replay from 0). There is also a new persisted per-database floor seam on IEventDatabase (FetchProjectionFloorAsync / TrySetProjectionFloorAsync / SetProjectionFloorAsync) and a new AsyncOptions.SubscribeFromFirstRun() strategy. Store implementations: JasperFx/marten#5740, JasperFx/polecat#813, JasperFx/fisher#471.IDocumentStoreDiagnosticsWriter.UndeleteDocumentAsync (#1059, #1062) and DocumentQueryOptions.OrderByMetadata (#1058, #1063).SkipApplyErrors, a non-transient DbException raised from projection code is no longer dead-lettered event by event. It pauses the shard with ShardFailure.IsTransient = false. ⚠️ This is a behaviour change on Polecat and Fisher. Marten follow-up: JasperFx/marten#5741.--key=value splits at the first = only, so connection strings passed by WebApplicationFactory no longer produce "Invalid usage" output (#1057, #1060).SoftDeleteCompliance, DocumentMetadataCompliance (#785, #1067) and ProjectionFloorCompliance (#1068). New undelete and metadata-ordering facts in DocumentStoreDiagnosticsCompliance. Everything new is gated off by default.SingleTenantedEventSlicingCompliance is [Obsolete] and will be removed in 3.0 (#727, #1066, #1065).PublishAot gate proving the AOT roots companion end to end, with a negative control (#777, #1069).No public members were removed or changed. Every member added to an existing interface has a default implementation (verified against 2.92.0 with a public-API diff and the contract ratchet), so stores built against 2.92 keep loading.
GH-1031 ( #1034 ): store-agnostic IEventStore.PreviewHighWaterAdvanceAsync and IEventStore.AdvanceHighWaterMarkToLatestAsync . They preview and advanc
IEventStore.PreviewHighWaterAdvanceAsync and IEventStore.AdvanceHighWaterMarkToLatestAsync. They preview and advance a database's high water mark (or one tenant's under per-tenant event partitioning) to the highest committed sequence, with an expectedCurrentMark compare-and-set. Both are default members that throw NotSupportedException until a store implements them. ProjectionHost.AdvanceHighWaterMarkToLatestAsync no longer throws NotImplementedException.HighWaterAgent: survive a failed watchdog restart ( #1027 ), and restart on a stalled mark by @jeremydmiller in #1028
Full Changelog: v2.90.2...v2.91.0
Full Changelog: https://github.com/JasperFx/jasperfx/compare/v2.90.2...v2.91.0
This stops a pretty substantial memory leak if you happen to be constantly starting and tearing down IHost instances in testing
This stops a pretty substantial memory leak if you happen to be constantly starting and tearing down IHost instances in testing
Full Changelog: V2.90.1...v2.90.2
#1020 (part of #1019 ): ProjectionExceptions.IsExceptionTransient also consults TransientFailures . A fault a store's classifier calls transient (a SQ
ProjectionExceptions.IsExceptionTransient also consults TransientFailures. A fault a store's classifier calls transient (a SQL Server deadlock in Polecat, SQLITE_BUSY in Fisher) is rethrown for retry/pause instead of being dead-lettered under SkipApplyErrors. Registered types still win; ApplyEventException is never transient.IEventStoreOperations.TombstoneStream(Guid|string) ( #1014 , #1017 ): a hard delete of a stream, its events and its tag rows, queued until SaveChanges
IEventStoreOperations.TombstoneStream(Guid|string) (#1014, #1017): a hard delete of a stream, its events and its tag rows, queued until SaveChangesAsync.
NotSupportedException until a store implements it.StreamTombstoningCompliance suite (9 facts) is gated on SupportsTombstoneStream.TagTypeRegistration.FromUnwrapper<TTag, TInner> (#1012, thanks @skoging): registers a DCB tag type from an explicit unwrapper, which is safe under Native AOT.TagTypeRegistration.Create<TTag> (#1018) is now annotated [RequiresUnreferencedCode] / [RequiresDynamicCode] instead of suppressing those warnings. A store's RegisterTagType<TTag> will raise IL2026/IL3050 warnings under IsAotCompatible.BlueGreenSideEffectGateTests race (#1018).ShardFailure.IsTransient : whether a shard's failure is expected to clear on its own. ( #1016 , for JasperFx/wolverine#4986 )
ShardFailure.IsTransient: whether a shard's failure is expected to clear on its own. (#1016, for JasperFx/wolverine#4986)
ShardFailure.For sets it from the exception graph, through the new TransientFailures.IsTransient(Exception). The failure is transient when anything in the inner exceptions or an AggregateException is one of these:
DbException that reports IsTransient;TimeoutException;SocketException;IOException that isn't a file system one.ShardFailureCategory.Other alone can't tell those two apart.Category, not a new category, so nothing that switches on the category changes. A failure serialized before this release reads back as false.TransientFailures.AddClassifier(Func<Exception, bool?>) is for a driver whose own IsTransient is weak. Probes against each store's pinned driver:
57P01 are transient; 42703 is not.IsTransient at all. Polecat and Fisher should each add a classifier.IProjectionDaemon.StartAgentInRebuildModeAsync(ShardName, CancellationToken) : start a projection shard in Rebuild mode that follows the store and res
IProjectionDaemon.StartAgentInRebuildModeAsync(ShardName, CancellationToken): start a projection shard in Rebuild mode that follows the store and resumes from its own progress. (#1015, for JasperFx/wolverine#4569)
ShardExecutionMode.Rebuild, so no side effects are published, and it keeps following the store past the high-water mark instead of stopping there.CatchUp: 0) and a rewind of the progression row, so a restarted Rebuild-mode shard replayed its history over the documents it had already built.StartAgentAsync continues in Continuous mode from the same progress.NotSupportedException, so other IProjectionDaemon implementations keep compiling.ProjectionSideEffectCompliance has three new facts covering the above: Rebuild mode follows the store without side effects, a restart resumes from its progress, and a Continuous restart continues from it. Stores pick them up with this package: JasperFx/marten#5668, JasperFx/polecat#768, JasperFx/fisher#441.IEventStore.TryDescribeDatabasesAsync(CancellationToken) : the database half of TryCreateUsage . ( #1013 , for JasperFx/wolverine#5002 )
IEventStore.TryDescribeDatabasesAsync(CancellationToken): the database half of TryCreateUsage. (#1013, for JasperFx/wolverine#5002)
DatabaseUsage: each database's server, name and tenant ids. It skips the highest event sequence and the descriptions of every projection, subscription, event type and tag type.TryCreateUsage()?.Database, so every existing store keeps working with no change.RegisteredShardNames(), for agent assignment on every leader heartbeat.SpecificationManifestAttribute moves into JasperFx, next to SpecificationBindingDescriptor .
SpecificationManifestAttribute moves into JasperFx, next to SpecificationBindingDescriptor.SpecificationManifest.In(assembly) and SpecificationManifest.Load(path) read the manifest. The reader also accepts Bobcat's older attribute by name.describe-event-model --specs and event-model --specs use it (JasperFx/wolverine#5004), and Bobcat writes the new attribute (JasperFx/bobcat#528).StartAgentAsync(ShardName) now throws ShardStartException with the new ShardStartFailureReason.Rebuilding , which is transient.
StartAgentAsync(ShardName) now throws ShardStartException with the new ShardStartFailureReason.Rebuilding, which is transient.ProjectionAlreadyRebuildingException.IProjectionDaemon.IsRebuilding(ShardName) is a new default interface member. (#1010)Also already in 2.85.0, and now closed: #1004 (an aggregate's identity type on the Event Model) and #1005 (IEventStore.FindDatabaseForTenantAsync).
A declared Human trigger is compatible with how the code receives it. Human against a derived MessageHandler , Http or Grpc no longer raises a SourceD
Human against a derived MessageHandler, Http or Grpc no longer raises a SourceDisagreement. The merged slice keeps the how on TriggerKind and the who on the new TriggeredBy. Human against JobScheduler/External still disagrees.HandlerMethod on slices and handler relationships names the user's handler or endpoint method. HandlerType is always the user's class, never generated code.@jasperfx/event-model-vue 0.15.0: wire types gain triggeredBy, handlerType, handlerMethod, readsFrom and PublisherOrigin.httpRouteName (#1007), and triggerOrigin is typed as the object it is.SlicePattern.Query ( #1003 ). A read-only endpoint now gets its own slice instead of being folded into a View. A Query reads its read model, aggregate
SlicePattern.Query (#1003). A read-only endpoint now gets its own slice instead of being folded into a View. A Query reads its read model, aggregate or document through ReadsFrom, and links to the View that produces it. A Query that emits events, starts a stream or publishes messages is flagged as a PatternViolation hotspot. Fluent API: Query<TReadModel>() and Query(name).AggregateDescriptor.IdentityType is derived from the aggregate's single-stream projection, or declared with model.Aggregate<Order>().IdentifiedBy<OrderId>(). A declared type that disagrees with the derived one is reported as a SourceDisagreement. The projection source now contributes one aggregate per single-stream projection.PublisherOrigin.HttpRouteName: an HTTP trigger can carry its ASP.NET Core route name.@jasperfx/event-model-vue 0.14.0 draws Query slices and pattern-violation hotspots, and adds SliceFilter.patterns.IEventStore.FindDatabaseForTenantAsync(tenantId) (#1005). A store-agnostic way to look up a tenant's database, as a default interface member: it returns the single database when that's certain, and null otherwise. Marten, Polecat and Fisher are expected to override it.Enumerable flags and arguments bind to array members ( #1002 ). The reflection command parser handed a List<T> to a T[] property, which threw, so --ch
List<T> to a T[] property, which threw, so --chapter A B on a string[] flag failed as Unknown argument or flag. An array member now gets an array, as the source-generated parser already did. Commands with a source-generated parser were never affected.JasperFx.Linq.DynamicQuery composes a predicate and an ordering written as text onto an IQueryable whose element type is known only at runtime, so the
JasperFx.Linq.DynamicQuery composes a predicate and an ordering written as text onto an IQueryable whose element type is known only at runtime, so the store's own LINQ provider does the translation. Built on System.Linq.Dynamic.Core 1.7.4. Docs: LINQ → Dynamic LINQ Queries.
new and no type lookup by name, then a post-parse allow-list (a short list of string and collection methods that must touch the document; no static members, conditionals, or construction beyond dates, times and Guids) and caps on text length, arguments and tree size.CreateQuery<T> (Marten's non-generic one throws).JsonElement arguments — what object?[] becomes after a JSON wire — are unwrapped.DynamicQueryException carries the clause, the reason and the parser's position.DynamicQueryPolicy.ShapeRules and DynamicQueryShapeRules let a store refuse shapes its provider would translate into the wrong rows. SqlNullSemantics() refuses an unguarded <> (or a negated comparison) on a nullable member: SQL's three-valued logic silently drops every null row, measured on Marten, Polecat and Fisher alike.DocumentQueryOptions.ApplyCriteriaTo / Untranslatable / IsTranslationFailure apply Where / OrderBy / Arguments and turn every failure into DocumentCriteriaNotSupportedException, which gains Position. Refused under Native AOT.DocumentStoreDiagnosticsCompliance gains twelve criteria facts. ComplianceDocuments.cs now declares #nullable enable, because it compiles inside the consumer.stream-query --where / --order-by over StreamState.[RequiresDynamicCode] / [RequiresUnreferencedCode]; the AOT smoke project stays green.⚠️ Every JasperFx consumer now picks up System.Linq.Dynamic.Core transitively (no dependencies of its own on net8+).
DcbModel<T>() as a synonym for DeciderModel<T>() on the event model slice builder.AsSingleStream() / AsMultiStream() / AsDcbModel().EventTagQuery.For(tag) selects events with that tag. Before, For(a) alone had no condition and For(a).Or(b) quietly queried b alone; For(...).AndEventsOfType<...>() queries are unchanged.DocumentCriteriaNotSupportedException.Position (init-only).JasperFx.Linq.IDynamicQueryShapeRule.EventModelRole.ViewProjection (2.83.0), appended so existing integer values don't change.Nothing published for this version
ForAggregate<T>() sets the default aggregate for the command slices declared after it.
Name join the application's model. EventModelDefinition.Name now defaults to the service name (JasperFxOptions.ServiceName), so a definition per chapter merges with the model derived from code. Before, each definition became its own model, named after its class.DiscoveredEventModels manifest per assembly. The new AddDiscoveredEventModels(assembly) registers definitions from it, without scanning types.ForAggregate<T>() sets the default aggregate for the command slices declared after it.NoAggregate() and DeciderModel<T>() override that default.AggregateDeclaration.LinksToSpecification<TSpec>(nameof(...)).SpecificationBindingDescriptor contract and EventModelSpecifications.Link join specs to slices by command type.Specified provenance rung ranks between Declared and Derived. Compare rungs with Rank() / Outranks(), not the raw enum value.UnresolvedSpecification hotspot.[assembly: EmittedEvents(...)].
ICarriesEvents marker.IRefersToAggregate marker rather than by attribute name.InMemoryDocumentStore implements IEventStore.These are appended enum members, so existing integer values don't change:
EventModelProvenance.SpecifiedHotspotOrigin.UnresolvedSpecificationEventModelRole.AggregateDeclaration and EventModelRole.DeciderModel⚠️ Behaviour change: daemon drains are bounded by StopAndDrainTimeout
StopAndDrainTimeoutStopAndDrainAsync now honours DaemonSettings.StopAndDrainTimeout (default 5 seconds) for both event subscriptions (#953) and async projection shards (#980).
What this means for Marten, Polecat and Fisher users:
ProgressionProgressOutOfOrderException and a Stopped shard.StopAndDrainTimeout is cancelled on every shutdown or rebalance and then run again. Delivery was always at-least-once, but duplicates will now happen more often for slow pages. Side effects outside the store session aren't rolled back, such as HTTP calls or sends that bypass the outbox. If your pages are slow, raise StopAndDrainTimeout.ProcessRangeAsync directly are unaffected.Downstream adoption: JasperFx/marten#5610, JasperFx/polecat#744, JasperFx/fisher#434.
JasperFx.Events.InMemory, a store for prototyping (#962)A new package with an in-memory document and event store, meant for short-lived prototyping, before you pick Marten, Polecat or Fisher. It is not meant for production use.
SaveChangesAsync is now all-or-nothing.StartStream/append, FetchForWriting/FetchLatest, live aggregation, and inline single- and multi-stream projections. It is validated against the event compliance suites.AddInMemoryStoreForPrototyping(...) with ConfigureDocuments, ConfigureEvents and ConfigureProjections.NotSupportedException.Command<T>(), Automation(..), View<T>(), Translation(..), Slice(name) and InChapter (#957).Origin on its slices (#959).[Domain] on handlers and endpoints (#960).SourceWriter output: no blank line before }, else, catch or the end of the file. END is only recognised as a whole directive, and there is now a way to emit a backtick (#956).ShardName construction is ~3–8x faster and TryParse ~2–4x faster, both with roughly half the allocations, which matters on stores with thousands of tenant shards (#952).BlockIdleWakeupTests inline-execution assertion (#973), and one in the BlueGreen gate test harness (#983).main and actually builds the docs (#794).Full Changelog: V2.80.1...V2.81.0
Nothing published for this version
ResilientEventLoader now wraps load failures in EventLoaderException ( #948 , #949 ). LoadAsync returned the Polly pipeline's task without awaiting it
ResilientEventLoader now wraps load failures in EventLoaderException (#948, #949). LoadAsync returned the Polly pipeline's task without awaiting it, and Polly captures even a synchronous throw into that task, so the wrap never ran at all. Shards saw the raw provider exception, without the shard name and database identifier. The method now awaits inside its try.
OperationCanceledException, so daemon shutdown paths keep treating it as shutdown, not as a shard failure.EventLoaderException (e.g. Marten's read policy and WriteRetryClassifier) will now see it on this path for the first time.Full Changelog: V2.80.0...V2.80.1
ValueTypeInfo strong-typed id wrappers now work under Native AOT ( #942 , #946 ). CreateWrapper<TOuter, TInner>() and UnWrapper<TOuter, TInner>() prev
ValueTypeInfo strong-typed id wrappers now work under Native AOT (#942, #946). CreateWrapper<TOuter, TInner>() and UnWrapper<TOuter, TInner>() previously always compiled via FastExpressionCompiler and threw PlatformNotSupportedException in a native image. They now branch on RuntimeFeature.IsDynamicCodeSupported, like LambdaBuilder, and fall back to invoking the resolved constructor, static builder, or value property through reflection. JIT behaviour is unchanged.JasperFx.Events.ComplianceTests)DocumentSearchCompliance gains hierarchy facts (#944, #945). Two new ComplianceMemory sub-classes and four facts, gated on SupportsDocumentHierarchies plus the search flags: sub-class vector search, root vector search, sub-class hybrid search, and a sub-class search filtering on the sub-class's own member. The facts assert a member only the requested sub-class carries, not just a count. ⚠️ Stores whose search path has no doc_type predicate will fail these (see polecat#723, marten#5440).GuidOptimisticConcurrencyCompliance covers the mapped version member (#943). It now covers a version mapped through the store's metadata (Metadata(m => m.Version.MapTo(...))) as well as the IVersioned marker interface. The mapped route is a separate code path that has broken four times across stores.Full Changelog: V2.79.2...V2.80.0
Native AOT: source-generated evolver constructors were trimmed, so PublishAot apps failed at startup with MissingMethodException . GeneratedEvolverAtt
Fix incorrect disposal of composite projection batches ( #939 , @Hawxy )
New policy: in a minor release, members added to existing interfaces get default implementations. A ratchet test now enforces this for every public in
IDocumentStoreDiagnostics.Subject and LoadDocumentAsync became abstract, so Marten 9.42 (and Polecat < 5.34, Fisher < 1.15) threw TypeLoadException at startup when resolved alongside JasperFx 2.77 or 2.78. Both members now have default implementations. On an older store, LoadDocumentAsync handles default-tenant loads through the store's own LoadDocumentJsonAsync, and anything it can't answer throws NotSupportedException with an upgrade message (#935).IDocumentReadOperations.LoadManyAsync<T> (Guid / string ids) and IEventStoreOperations.FetchManyForWriting<T> (Guid / string ids: one handle per id, in order, each with its own version check). Both have default implementations that make one call per id; stores override them for a single round trip. Compliance coverage is included (#934).DocumentTypesAsync lists sub-classes. New DocumentTypeRef.RootTypeName / IsSubClass (#936).marten#5550, polecat#712, fisher#374 (native batch reads); marten#5551, fisher#375, polecat#713 (sub-class listing); CritterWatch#1376, #1377.
GH-928 : DocumentQueryOptions.AllTenants , an explicit all-tenants scope for IDocumentStoreDiagnostics , plus AssertValidTenantScope() and compliance
IDocumentStoreDiagnostics grows up ( #870 , #927 )
IDocumentStoreDiagnostics grows up (#870, #927)The store-agnostic document diagnostics contract that CritterWatch uses:
DocumentQueryOptions gains Where, OrderBy, Arguments (Dynamic LINQ text, per #869) and IncludeSoftDeleted. If a store can't apply a filter, it must throw the new DocumentCriteriaNotSupportedException instead of returning an unfiltered page.Subject URI, which pairs with IDocumentStoreUsageSource.Subject so a console can target the main store or an ancillary one.DocumentQueryOptions.NormalizeTenantId).LoadDocumentAsync(type, id, tenantId) returns a StoredDocument. LoadDocumentJsonAsync now forwards to it.StoredDocument rows (version, last modified, created, tenant, deleted and deleted-at, .NET type) are on DocumentQueryResult.Documents.IDocumentStoreDiagnosticsWriter saves from JSON and deletes, with an expected-version check and a tenant.DocumentStoreUsage.SerializerCasing, plus structured Indexes and DuplicatedFields on DocumentMappingDescriptor.DocumentStoreDiagnosticsCompliance suite, with SoftDeleted<T>() and AddSubClass<TRoot, TSub>() on DocumentComplianceConfig.⚠️ Breaking for implementers:
IDocumentStoreDiagnostics.SubjectandLoadDocumentAsyncare abstract on purpose, so Marten, Polecat and Fisher all adopt the contract in the same wave. Tracking issues: JasperFx/marten#5543, JasperFx/polecat#706, JasperFx/fisher#364.
ShardState.LastUpdated (#924, #926): the progression row's last_updated now flows through AllProjectionProgress, which gives a signal for whether a shard is still alive.ProjectionDeleted on the async-daemon path (#917, #925). This is the deferred half of #893.EventTypes (marten#3942, #923).All seven are at 2.77.0. JasperFx.RuntimeCompiler is versioned independently and is unchanged.
Full Changelog: V2.76.1...V2.77.0
DatabaseUri() no longer throws on SQL Server named instances, LocalDB, or SQL Express ( #918 , #919 ). Server names such as db-host\MSSQL2017 , .\SQLE
DatabaseUri() no longer throws on SQL Server named instances, LocalDB, or SQL Express (#918, #919). Server names such as db-host\MSSQL2017, .\SQLEXPRESS, and (localdb)\MSSQLLocalDB used to throw Invalid URI: The hostname could not be parsed. That stopped Wolverine hosts with a SQL Server outbox from starting (wolverine#4685). The host is now sanitized to the characters a URI host allows, instead of being escaped.resources -t is the type filter again (#921, #922). --timeout and --type both claimed -t, so resources setup -t Wolverine was read as a timeout and threw. --timeout is now long-form only.resources command is documented (#920, #922). The new Stateful Resources page covers the command's actions and flags, startup setup with AddResourceSetupOnStartup and StartupAction, the IHost test helpers, and writing your own IStatefulResource.IEventStore.CompactStreamAsync is tenant-aware ( #910 ) — a compaction policy selecting streams in a tenant scope can now compact them, including when
IEventStore.CompactStreamAsync is tenant-aware (#910) — a compaction policy selecting streams in a tenant scope can now compact them, including when the default tenant is disabled.IEventStore.HasEventStore (#914) — a store-agnostic signal that a store actually has an event store, so monitoring can skip document-only stores.ShardStartException carries a classified reason (#912) — transient vs configuration vs paused, instead of prose only; the constructor is now public.IAdvisoryLock.FindHolderAsync (#913) — ask who holds a projection distribution lock. The default throws NotSupportedException; Weasel implements it for Postgres and SQL Server (weasel#650).Store implementations: marten#5527, polecat#698, fisher#354, weasel#650.
A patch release. One user-facing diagnostic fix that neither 2.75.0 nor 2.75.1 helps with , plus a new build warning.
A patch release. One user-facing diagnostic fix that neither 2.75.0 nor 2.75.1 helps with, plus a new build warning.
If you hit that exception on a projection registered as Snapshot<T>(), SingleStreamProjection<T, TId> or AggregateStream<T>, the message said:
The JasperFx.Events source generator DID run over assemblies YourApp and Marten, so it saw the aggregate YourApp.MyAggregate and declined it — this is a code-shape problem, not a build configuration one.
For that registration shape the verdict was inverted. The projection type is the store's own generic, so its assembly is Marten.dll — and Marten's build runs the generator, so that assembly always carries the marker #887 introduced. The verdict was therefore pinned to "the generator ran" for the commonest registration shape in the product, and you were sent to audit your aggregate's method shapes while being explicitly told that the cause you actually had was not the cause.
marten#5495 is exactly this shape. #887 was filed out of it, so as shipped it would have misdirected the very reporter it was written for — and for this shape it was worse than the nine-line hedge it replaced, which at least named the csproj cause among the others.
Neither earlier release helps: AggregateApplication.cs is byte-identical across 2.75.0 and 2.75.1. If you are debugging a missing dispatcher, this is the bump you want.
Fixed by excluding constructed generic projection types from the evidence. Deliberately not by requiring confirmation everywhere: a user-declared MyProjection : SingleStreamProjection<Agg, Guid> in its own assembly really does get a projection-specific evolver emitted there, so confirmation in that assembly stays genuine evidence — a fact now guards that case explicitly. #906.
Two copies of JasperFx.Events.SourceGenerator in one compilation emit byte-identical file paths, and the file-scoped evolvers mangle to the same name, so the build fails with
error CS0433: The type 'XEvolver' exists in both 'YourAssembly' and 'YourAssembly'
— one assembly named twice, which is the fingerprint. Nothing in that message mentions the generator, the two copies, or the remedy.
2.75.0's MSBuild target already prevented this by keeping one copy, but the states that actually produce the CS0433 are the ones where that target did not run — and there it said nothing. Detection is now separate from the fix: JasperFxEventsDedupeSourceGeneratorAnalyzers=false opts out of the dedupe, not the diagnosis, and a duplicate now warns JFXEVT902 naming both paths, the error to expect, and the remedy (a store package bundles the analyzer, so dropping a direct PackageReference on JasperFx.Events.SourceGenerator usually resolves it).
Stated plainly, because it is a real limit: that covers MSBuild builds only. A consumer on a JasperFx.Events predating the target, or a compilation running no MSBuild targets, reaches the same CS0433 with nothing of ours present to warn. So the generated marker file now carries a header explaining the error — which reaches those cases, because the generator running twice is what a double load is, so that file exists in exactly the states where the CS0433 happens. #902.
The shipped JasperFx.Events.targets is now imported and exercised by ./build.sh Test in six arrangements (#908). It ships as buildTransitive, so it reaches every consumer of the stack transitively — but as <None> rather than an <Import>, so our own build never loaded it and could not tell whether it was even well-formed XML. A malformed version passed the entire suite here while breaking every consumer's build, which is not hypothetical: it happened once while writing the JFXEVT902 warning above, and was caught by hand. Now it is caught by CI. No packaged content changed.
Unaffected by this patch: JasperFx/marten#5517, JasperFx/polecat#682, JasperFx/fisher#336 — enrollment of 2.75.0's DocumentConjoinedTenancyCompliance, plus replaying 2.75.1's new ComplianceStoreConfig.AddCommitListener in each event fixture.
A patch release. One runtime fix, and one correction to a compliance fact that 2.75.0 shipped in a state no store could pass — read the first section
A patch release. One runtime fix, and one correction to a compliance fact that 2.75.0 shipped in a state no store could pass — read the first section if you enrolled the new document tenancy suite.
DocumentConjoinedTenancyCompliance on 2.75.0, one of its ten facts could not passoptimistic_concurrency_is_scoped_to_the_tenant_for_a_shared_id asserted a refusal no correct store can produce. It advanced tenant A's row by storing a loaded instance, then re-stored that same instance and expected a ConcurrencyException — but a committed Store writes the landed version back onto the instance, so the guard matched the current version and the write was admitted.
That write-back is not incidental, it is required: GuidOptimisticConcurrencyCompliance.a_successful_write_moves_the_instances_own_version_on mandates it, so that a long-lived instance stays usable. The two facts contradicted each other, and no store could be green on both. The only way to pass the tenancy fact was to fail the concurrency suite it is a tenanted special case of.
This was our bug, not yours. A red fact there needed no change on your side, and no store behaviour was wrong. Because JasperFx.Events.ComplianceTests ships as source, the fix arrives by bumping to 2.75.1 — nothing else to do.
Fixed by making "stale" mean a separately loaded instance, read before the winning write, which is what stale has to mean on a store with write-back. The arrangement that gives the fact its teeth — one document id shared across two tenants — is unchanged.
The fact skipped in this repository, because the in-memory reference store left SupportsOptimisticConcurrency false. A fact that skips everywhere it could run is a fact nobody has checked, and this one reached three stores that way.
So the reference store now implements the IVersioned guard and enrolls GuidOptimisticConcurrencyCompliance alongside the tenancy suite. It had to be enrolled in both, because the contradiction is between two suites — nothing enrolled in only one can see it. Reverting the suite to its 2.75.0 text now fails in this repo with the same symptom reported against Fisher.
That work also exposed a second defect in the reference store: LoadAsync handed back the stored object reference, so two independent reads were one object and could never disagree about a version. Documents now round-trip through JSON on read and write, as a real store does.
#903.
Block<T> workers no longer inherit the activity current when the block was builtBlock<T> starts its workers with Task.Run in the constructor, and Task.Run flows the ExecutionContext — so every worker captured whatever Activity.Current was set at construction and kept it for the block's whole lifetime, long after that activity had ended. Every span the block's action started became a child of it.
The reported consequence: a Marten async daemon whose projection agents were rebuilt from inside a Wolverine HTTP handler parented every subsequent projection page span under that one request — 3,943 spans in ten minutes, on a trace already reported as finished. Anyone restarting projection agents from a request-scoped context was affected.
The ambient activity is now cleared per item, so each posted item's work is a trace root. Per item rather than once per worker because an action that starts an activity and does not dispose it would otherwise leak into the next item's parentage.
ExecutionContext.SuppressFlow() would have fixed the symptom too and was deliberately not used: it stops every AsyncLocal from reaching the workers, logging scopes and the current culture included, and a caller relying on those would lose them silently. Clearing one ambient value changes nothing else a worker inherits, and nothing at all for the caller.
Reported with a complete repro, the correct diagnosis and the fix taken here by @smoqmilus. #900.
Two facts were passing regardless of whether the behaviour they name was correct. Both are replaced or joined by versions that fail on a broken runtime — verified by reverting the relevant fix and re-running, not by inspection.
creating_and_deleting_within_one_batch_reports_no_deletion (#893) asserts what a commit reported rather than what it stored. Its predecessor passed either way, because inline the phantom delete targets a row that does not exist and is a no-op in SQL — but the deletion still appears in IDocumentChangeSet.Deleted, which is how #886's reporter found it. Confirmed to fail with #889's runtime fix reverted, while the old fact still passed.a_project_with_no_aggregates_builds_clean_under_the_double_load (#887) pins JasperFxSourceGeneratorAppliedAttribute's AllowMultiple = true in the one topology where the marker is the only thing emitted twice. The existing fact asserted "no CS0579" inside a build already broken by CS0433, so it would have passed if the rule regressed.ComplianceStoreConfig.AddCommitListener(...) — the event-store twin of the document config's listener slot. Each store's event fixture needs to replay it (options.AddCommitListener(listener) on Marten, one call identical to what each document fixture already makes). Until a store does, the new fact fails rather than skips, by the #672 rule.
Still open, and unaffected by this patch: JasperFx/marten#5517, JasperFx/polecat#682, JasperFx/fisher#336. The Polecat one is not just enrollment — document tenancy there is taken from the event store's, store-wide, with no per-type opt-in.
Conjoined document tenancy, and tenancy past the event read path ( #898 , #899 )
JasperFx.Events.ComplianceTests covered conjoined events well — twelve facts, enrolled by all three stores — and the document side had no tenancy seam at all. This release closes that, and extends the event suite past reads.
DocumentConjoinedTenancyCompliance (10 facts)Every fact checks both directions and reuses one document id across two tenants. The second is load-bearing: a store keying documents on id alone does not fail loudly, it folds the two writes into one row — so the second silently overwrites the first and both tenants then read the same document. Distinct ids per tenant, which every tenanted fact used before, passes cleanly on exactly that store.
Covers every read shape with no Where (the fisher#51 leak), LoadAsync on all three identity overloads, insert and update of a shared id, all three Delete routes, tenant-scoped optimistic concurrency and numeric revisions, and the AnyTenant / TenantIsOneOf escapes.
ConjoinedEventTenancyComplianceinline_and_async_snapshots_of_a_shared_stream_id_stay_isolated_per_tenant — no fact anywhere had registered a projection and written one stream id in two tenants, so a store projecting into a single-tenanted snapshot table passed everything. Both lifecycles, since the inline write knows its tenant and the async write must reconstruct it.async_rebuild_across_many_tenants_produces_one_document_per_tenant_stream — 200 tenants share one stream id, making the count an assertion: 200 documents on a correct store, exactly 1 on a broken one.with_the_default_tenant_disabled_every_read_route_is_reachable_through_a_tenant_scope — the first assertion anywhere of ComplianceExceptionKind.DefaultTenantUsageDisabled, declared and never used until now.projection_side_effect_messages_carry_the_event_tenant — the shared RecordingMessageOutbox was receiving the tenant id and discarding it.IDocumentSessionFactoryGains LightweightSession(string tenantId) and QuerySession(string tenantId), with throwing defaults, so nothing breaks on the bump.
A store implementing IDocumentSessionFactory<TOperations, TQuerySession> must write the explicit non-generic forwarders, exactly as it already does for the parameterless pair:
IDocumentSessionOperations IDocumentSessionFactory.LightweightSession(string tenantId)
=> LightweightSession(tenantId);C# interface implementation is not return-type covariant, so a product-typed member satisfies only the generic interface and leaves the contract member on the throwing default — on tenancy that is otherwise perfectly correct. Same near-miss as IDocumentReadOperations.Events. DocumentSessionFactoryDefaultsTests pins the shape.
DetermineAction's action per batch, not per eventIEventStore.OpenReadOnlyEventStore(tenantId)JasperFx/marten#5517, JasperFx/polecat#682, JasperFx/fisher#336. The Polecat one is not just enrollment — document tenancy there is taken from the event store's, store-wide, with no per-type opt-in.
…tenant and a store can adopt it without a breaking change.
An exception-diagnostics release. Seven issues from the 2026-09-22 sweep, all of them about the same thing: a Critter Stack failure naming the fact and stopping, where it could have named the remedy — plus one duplicate type name that made a catch ambiguous.
Nothing here changes how any store reads or writes data.
JasperFx.Events.ArchivedStreamException (#871). Three stores refused an append to an archived stream with three unrelated types — Marten's generic InvalidStreamOperationException, Polecat's InvalidStreamException, Fisher's own ArchivedStreamException — and none was on the shared surface. Fisher's shape is the canonical one, because only its message names the way back:
Event stream '{id}' is archived and cannot be appended to. Call UnArchiveStream to reopen it, or start a new stream.
JasperFx.MultiTenancy.DisabledTenantException (#875). A tenant that exists and was deliberately disabled is reported as unknown by Marten and Polecat, so the operator who just ran CritterWatch's disable_tenant — or the on-call engineer after them — reads "Unknown tenant id 'acme'" about a tenant that is still there:
Tenant '{tenantId}' is registered but disabled, so this store will not open a session for it. Re-enable it through the tenancy source that owns it; its data is untouched.
It derives from UnknownTenantIdException, so an existing catch (UnknownTenantIdException) keeps catching a disabled tenant and a store can adopt it without a breaking change.
Both carry a protected message-overriding constructor, the same seam the six exceptions lifted in #751 use, so a store whose wording diverged can subclass without breaking its own message assertions.
ExistingStreamIdCollisionException and NonExistentStreamException (#872). Polecat and Fisher inherit these through their subclasses, so both pick the remediation up without a change on their side; Marten keeps its own wording.
The second one is the costly case. Plain Append is deliberately start-or-append on every store, so the only way to reach the exception is AppendOptimistic / AppendExclusive — and the bare fact reads as "Append needs StartStream first", sending people to change code that was fine. The message now names the overloads that actually require an existing stream.
UnknownTenantIdException (#874). The canonical message gains a remedy sentence covering the three things it could mean — never registered, registered under a different casing, or disabled — and a new UnknownTenantIdException(string tenantId, IReadOnlyCollection<string>? knownTenantIds) overload lets a source that holds its tenants in memory list them: It knows: one, two. Sources that would have to hit the database pass null.
⚠ Behaviour change: StaticTenantSource<T>.FindAsync now throws UnknownTenantIdException instead of ArgumentOutOfRangeException. Every store already threw the shared type for this condition; the one tenancy source JasperFx ships itself did not, so a caller catching the shared type was missing the shared implementation. If you catch ArgumentOutOfRangeException around StaticTenantSource.FindAsync, change it.
JasperFx.RuntimeCompiler.CodeGenerationException now derives from JasperFx.CodeGeneration.CodeGenerationException (#877). Two public classes shared the simple name, so catch (CodeGenerationException) caught whichever one a file's using directives happened to resolve, and a stack trace naming it was ambiguous. Deriving — the RuntimeCompiler one is the same class of failure one layer down — makes a single catch cover both, with no rename and no obsoletion cycle. It also exposes Subject now.
ComplianceExceptionKind.ArchivedStream joins the six existing categories, defaulting to ArchivedStreamException, and StreamArchivingCompliance.appending_to_an_archived_stream_is_rejected asserts the nominated type instead of "something threw".
⚠ For store maintainers: that assertion has teeth now. A store that neither subclasses ArchivedStreamException nor points ExceptionTypeFor(ComplianceExceptionKind.ArchivedStream) at its own type will fail that one compliance fact. Marten will always name its own type there — all_exceptions_should_derive_from_MartenException plus single inheritance — which is exactly what the seam exists for.
AutoCreate XML comments now describe what Weasel actually does (#873). CreateOrUpdate was documented as purely additive; its Update delta drops columns, indexes and foreign keys the model no longer declares. None was documented as throwing on drift; it does not — the lazy path returns untouched, the explicit apply paths (db-apply, resources setup, ApplyAllConfiguredChangesToDatabaseAsync) coerce it to CreateOrUpdate, and only AssertDatabaseMatchesConfigurationAsync / db-assert reports drift. Both wordings came from Weasel's and Marten's own docs, so the same correction is queued there.TenantIdStyle (both defaulting to CaseSensitive); Polecat and Fisher do not have it and are split down the middle — the database-per-tenant lookup is case-insensitive while the conjoined tenant_id comparison is exact, so a mixed-case id finds the right database and then writes rows the other spelling cannot see. Until every store honours one knob, that table is the specification. Normalize tenant ids at the edge of your own system.docs/codegen/aot.md now records that TypeLoadMode.Auto degrades to the static loader inside a Native AOT image while an explicit TypeLoadMode.Dynamic throws PlatformNotSupportedException. No code change — the behaviour was already deliberate.Seven packages at 2.74.0: JasperFx, JasperFx.Events, JasperFx.Events.ComplianceTests, JasperFx.Events.SourceGenerator, JasperFx.SourceGenerator, JasperFx.Aspire, JasperFx.Events.MicrosoftExtensionsAI. JasperFx.RuntimeCompiler is versioned independently and stays at 5.0.0.
Note: 2.73.2 was published to NuGet without a tag or a GitHub release; this release does not restate it. Nothing shipped in 2.73.2 is missing from 2.74.0.
Backfilled on 2026-09-22. 2.73.2 was published to NuGet on 2026-09-18 without a tag or a release entry. This tag and these notes were reconstructed af
Backfilled on 2026-09-22. 2.73.2 was published to NuGet on 2026-09-18 without a tag or a release entry. This tag and these notes were reconstructed afterwards from the commits between V2.73.1 and
3fb8de4, so that the version on NuGet has something to point at. The packages themselves are untouched and are the ones published on the 18th.
A single-fix patch over 2.73.1.
codegen test no longer fails on an app with message handlers (#867)Fixes wolverine#4486.
codegen test compiles every ICodeFile into its own in-memory assembly. When an AotRoots companion rooted a sibling generated type by name (AttributeArg.TypeNamed), that name lived in a different assembly and the compile failed with CS0234. Since Wolverine 6.37, HandlerRegistryCodeFile roots every generated message handler this way — so codegen test failed for any app with message handlers, while codegen write plus a build worked fine.
The fix adds a GeneratedAssembly.CompiledInIsolation flag that only TryBuildAndCompileAll sets; when it is set, AddAotRoots drops the TypeNamed roots that do not resolve within the assembly being compiled. Roots to existing Types and to the file's own generated types are kept.
The write paths are deliberately untouched — codegen write and Auto-mode CompileAndAttach write what they compile, so they still emit every root into the file the trimmer sees. Verified against four real services on Wolverine 6.39 / Marten 9.37: codegen test went from 19 × CS0234 to passing, and codegen write output was byte-identical, all 20 generated-type roots present.
Wolverine needs no change of its own — only this version.
Three other commits landed in this range and change nothing a NuGet consumer sees: the move of @jasperfx/event-model-vue into this repo (#864), and two documentation corrections to that package's publish workflow about npm trusted publishing (#865, #866 — the cause turned out to be the capitalisation of the GitHub owner in the npm binding).
Seven packages at 2.73.2: JasperFx, JasperFx.Events, JasperFx.Events.ComplianceTests, JasperFx.Events.SourceGenerator, JasperFx.SourceGenerator, JasperFx.Aspire, JasperFx.Events.MicrosoftExtensionsAI. JasperFx.RuntimeCompiler is versioned independently and stays at 5.0.0.
A binary-compatibility patch over 2.73.0 . 2.73.0 has been unlisted on NuGet — use this instead. No functional change beyond the constructor described
A binary-compatibility patch over 2.73.0. 2.73.0 has been unlisted on NuGet — use this instead. No functional change beyond the constructor described below; everything 2.73.0 shipped is here.
EventModelClaim gained a third, defaulted parameter (Source, from #861). That is a source-compatible change and a binary-breaking one: a record emits a single constructor, so the two-argument signature 2.72.0 published stopped existing. An assembly compiled against 2.72.0 that constructs a claim got a MissingMethodException rather than picking up the default.
An explicit two-argument constructor delegating to the primary one, restoring the 2.72.0 signature:
public EventModelClaim(EventModelProvenance provenance, string value)
: this(provenance, value, null) { }⚠ If you are tempted to make the same change elsewhere, it needs one more thing. A second parameterized constructor makes System.Text.Json refuse the type outright:
NotSupportedException : Deserialization of types without a parameterless constructor, a singular parameterized constructor, or a parameterized constructor annotated with 'JsonConstructorAttribute' is not supported. Type 'EventModelClaim'.
Every descriptor carrying a SourceDisagreement would have failed coming back off the wire — the path into CritterWatch and Bobcat. The primary constructor is therefore marked [method: JsonConstructor], the same pairing SpecificationDescriptor has carried in that folder for the same reason.
Deconstruct's arity changed the same way and is left alone. A two-output overload would silently drop Source for anyone destructuring a claim in new code, which is the loss #859 exists to stop, and nothing in the Critter Stack deconstructs a claim. If you do, recompile.
So: the constructor surface is restored, not the whole 2.72.0 surface.
Seven packages at 2.73.1: JasperFx, JasperFx.Events, JasperFx.Events.ComplianceTests, JasperFx.Events.SourceGenerator, JasperFx.SourceGenerator, JasperFx.Aspire, JasperFx.Events.MicrosoftExtensionsAI. JasperFx.RuntimeCompiler is versioned independently and stays at 5.0.0.
Full Changelog: V2.73.0...V2.73.1
⚠ Unlisted — use 2.73.1 instead
⚠ Unlisted — use 2.73.1 instead
This release is unlisted on NuGet.
EventModelClaim's two-argument constructor stopped
existing here (a defaulted third parameter on a record's primary constructor is binary-breaking),
so an assembly compiled against 2.72.0 that constructs one gets aMissingMethodException.
2.73.1 restores it and is otherwise
identical to what is described below. See the binary-compatibility note at the end of these notes.
Three Event Modeling / event sourcing changes, all additive.
StubEventStream<T> (#858, #862)JasperFx.Events.StubEventStream<T> is a stand-in for IEventStream<T> for unit testing a handler that takes a stream handle directly — Wolverine's [WriteAggregate] IEventStream<Account> account. Construct one with the aggregate state the handler should see, call the handler, assert on EventsAppended. No database, and no mocking library.
The stand-in previously existed only as Marten.Events.StubEventStream<T>, built on Marten's StoreOptions / EventGraph, so Polecat and Fisher users wrote their own or mocked the interface — and Received(1).AppendOne(...) proves only that a method was called, leaving which event and what it carried unchecked. EventRegistry builds IEvent envelopes with no store behind it, which is what made this liftable.
Id, Key, StartingVersion, CurrentVersion, Cancellation and AlwaysEnforceConsistency are settable for multi-stream and version-sensitive handlers; TryFastForwardVersion() is inert. Marten.Events.StubEventStream<T> is untouched and keeps compiling.
New docs page: Event Sourcing → Unit Testing Handlers.
Pattern: Declared claims Automation; Declared claims Command named neither party and read as one source contradicting itself. EventModelProvenance is a rung, and a rung holds several sources — spec-first work has a declared model file and specs, both Declared by construction.
EventModelClaim now carries a Source beside its Provenance, populated by the merge from the contributing slice's Origin, and Claimant renders the source where there is one and the rung otherwise:
Pattern: file://CritterCrush.emodel.yaml claims Automation; suite://CritterCrush.Specs claims Command
Two anonymous sources on one rung now say so (two Declared sources disagree — kept X, dropped Y) rather than naming the rung twice, and one source genuinely contradicting itself is the only case that reads that way. A source that never stamped Origin renders exactly as before.
ModelCollapse carries its model names as data (#853, #860)HotspotDescriptor.ModelCollapse recorded which Event Models were folded only inside Text, so a consumer that wanted to act on it — offer a picker, route per model, count them — had to regex a sentence. ServiceName and CollapsedModelNames now sit beside an unchanged Text.
HotspotDescriptor's equality is hand-written as a result, comparing CollapsedModelNames element-wise: a record compares a collection member by reference, which would have broken JSON round-trip equality and hotspot de-duplication. The merge itself de-duplicates on Origin + Text, never on equality.
EventModelClaim is a positional record and gained a third parameter (Source, defaulted), so its primary constructor's signature changed. Source-compatible — new EventModelClaim(rung, value) still compiles — but an assembly compiled against 2.72.0 that constructs one will need a recompile rather than a drop-in swap. Construction is almost entirely internal to JasperFx; reading the properties is unaffected.
Seven packages at 2.73.0: JasperFx, JasperFx.Events, JasperFx.Events.ComplianceTests, JasperFx.Events.SourceGenerator, JasperFx.SourceGenerator, JasperFx.Aspire, JasperFx.Events.MicrosoftExtensionsAI. JasperFx.RuntimeCompiler is versioned independently and stays at 5.0.0.
Full Changelog: V2.72.0...V2.73.0
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Event Modeling attribution and multi-model hosting.
Event Modeling attribution and multi-model hosting.
EventModelSliceDescriptor.Origin), alongside which provenance rung it sits on. ProjectionEventModelSource stamps it, and its dedupe records a SourceDisagreement hotspot when it drops a duplicate document name from a different store instead of discarding it silently.EventModelSetDescriptor pairs a service with every Event Model it hosts, so a modular monolith no longer has to lose a model name to fit a wire that carries one. EventModelDiscovery.AssembleSetAsync returns the pair; Find/Sole let a single-canvas consumer choose a model, and Collapse() is the explicit fold that records a ModelCollapse hotspot naming what went in.Both new enum values are appended and Origin is additive on the wire, so existing payloads and consumers are unaffected.
Two fixes and a documentation correction.
Two fixes and a documentation correction.
Thanks to @AllainPL for the diagnosis, the provenance and a deterministic repro.
MethodFrameArranger.compileFrames step 3 enumerated DependencyGatherer.Dependencies, an ImHashMap keyed by Frame. Frame does not override GetHashCode, so that walk followed identity hash codes and differed between two arrangements of the same logical method — and step 4's topological sort preserves the relative order of independent frames, so the emitted body carried the variation. #196 fixed exactly this for DependencyGatherer.Variables, which is why constructor parameters and fields have been stable and the statements inside the method were not.
Measured on a real application with committed generated code, running codegen write twice in the same environment: 15 of 60 files differed at 1.24.1, 6 of 60 still differed at 1.31.0 (the first release carrying #196). What was left moving is statement order. This also closes out JasperFx/wolverine#3059, which reported the same drift as a macOS-vs-Linux difference and guessed at the cause without a repro.
The fix walks frames and indexes the cache rather than enumerating the cache. The cache's keys are exactly the frames passed in — DependencyGatherer's constructor fills one entry per frame and nothing adds a key before step 3 — so the set gathered is unchanged and only the order becomes deterministic.
⚠️ Expect a one-time diff. If you have generated code committed, regenerating on 2.69.2 may reorder statements within a method once as they settle into a stable order. That is this fix landing, not a semantic change. Subsequent regenerations are byte-identical — which is the point: a drift check in CI, a code review, or a reproducible build can now tell a real change from hash-order noise.
SupportsMultipleDatabasesThe remarks said "Fisher is legitimately false — one file, one database." Fisher has had database-per-tenant since fisher#47 and runtime tenants since fisher#58, and both arms of MultiDatabaseExplorerCompliance are green there. Replaced with the store-neutral condition, plus the part that makes it matter: a Fisher tenant is a file, so this is the one suite in the set whose precondition is nearly free there and expensive on the other two — the opposite of what the old sentence implied.
WaitForNonStaleProjectionDataAsync's contract is now stated on the fixture seam: wait on every configured shard, not every shard that has reported. An implementation that gates on the rows it finds is satisfied by a store where one projection reached the head and another never ran — the wait returns and the next read sees a document that was never written. polecat#602 shipped that defect.
Found while wiring ProjectionEventModelSource into Fisher. JasperFxSingleStreamProjectionBase.determineEventTypes() concatenates both stream lifecycle
Two fixes on top of 2.69.0.
ConsumedEvents carried Archived and Compacted<T>Found while wiring ProjectionEventModelSource into Fisher. JasperFxSingleStreamProjectionBase.determineEventTypes() concatenates both stream lifecycle events onto every non-empty apply set, so an aggregate declaring exactly two Apply methods yielded a View slice consuming four event types. Honest about what the projection handles; not what an Event Model canvas means by the events a read model consumes — they render as stickies for events the application never wrote and no command slice emits, so they link to nothing.
Filtered in ProjectionEventModelSource.ToSlice, and deliberately not in the reader that fills AppliedEvents: Compacted<T> is a real stored event, the same reader feeds AggregateDescriptor.AppliedEvents, and a monitoring console asking "what does this projection handle" wants both. The narrow question is the canvas one, so the judgement sits with the thing drawing it. SubscriptionDescriptor.AppliedEvents is unchanged.
Matched on type identity — typeof(Archived).Assembly and typeof(Compacted<>).Name — so an application type called Archived keeps its sticky, and a rename upstream cannot leave a stale string behind.
Downstream: Fisher's event_model_source.a_registered_projection_becomes_a_view_slice asserts Archived is present, so that test moves when Fisher takes this version (JasperFx/fisher#251).
JasperFxSubscriptionBase's ILoggerFactory BuildExecution overload handed SubscriptionExecution<T> the database where its sibling hands the store — and the store is what implements ISubscriptionRunner<T>. That overload threw on construction, unconditionally.
JasperFxAsyncDaemon.buildAgentForShard picks it whenever the daemon was built with a logger factory — the hosted / projection-coordinator path — so on Marten, Polecat and Fisher alike a subscription registered that way never ran. It surfaced as a logged shard start failure rather than a crash: the app came up and the subscription silently did nothing.
Every other ISubscriptionFactory in the tree already passed store from both overloads; this one was the lone outlier.
Validated before release by packing locally and building against Marten, Polecat and Fisher.
#818 — ProjectionStatusCompliance, and a ruling on what ShardStatus means. Three stores had independently decided what the same five fields meant. ShardStatus.State is now a fact about the running daemon: a store that can reach one reports what it says, a store that cannot reports Unknown, which is distinct from Stopped. The inventory is projections, not shards. Reading statuses never starts a daemon, and EventStoreSequence is the head of the store rather than the high-water row. New ShardStatusState vocabulary. Downstream: marten#5383, polecat#589, fisher#243.
#819 — GuidOptimisticConcurrencyCompliance. There was no shared suite for Guid optimistic concurrency on any store, and two stores shipped the same field broken in two different ways (fisher#245, marten#5372). Five paired facts, plus DocumentComplianceConfig.UseOptimisticConcurrency<T>() / UseNumericRevisions<T>().
#810 — multi-database arms for the explorer reads. DatabasePerTenantExplorerCompliance pins that a store-global read on a multi-database store is not a silent partial answer; ShardedTenancyExplorerCompliance pins the tenant_id predicate on a store where many tenants share a database. New seams: ComplianceStoreConfig.TenantDatabases, SupportsMultipleDatabases, DatabaseForTenantAsync.
#823 — EventModelDescriptor.Links. Cross-slice cause→effect relationships, computed on read from the roles slices already stamp and never accepted as input. The join is public and pure (EventModelLinks.Compute) so consumers share one rule rather than keeping copies.
#824 — ConsumedEvents, ReadsFrom, Chapter. The vocabulary recorded what a slice produced and never what it read, so the State View arrow and the Automation input edge could not be drawn at all.
#825 — ProjectionEventModelSource. The store-derived rung: one View slice per registered projection, read out of IEventStore — so a View slice no longer appears on a canvas only when a human wrote one down. Store-agnostic; merges by document-type name with a spec-declared slice.
Validated before release by packing locally and building against Marten, Polecat and Fisher.
Two additions to the store-agnostic IEventStore surface, both driven by what a monitoring console that ships one assembly against Marten, Polecat and
Two additions to the store-agnostic IEventStore surface, both driven by what a monitoring console that ships one assembly against Marten, Polecat and Fisher alike cannot reach today. Additive and non-breaking — every member is a default interface implementation.
IEventStore.RegisteredShardNames() (#815, #816)AllShards() is declared only on IEventStore<TOperations, TQuerySession>, so reaching it means naming a closed generic per store. RegisteredShardNames() is the non-generic way in, and it supplies the expected half of the expected-versus-observed correlation that IEventDatabase.FetchProjectionLagAsync already performs against one database's progression rows — the half that lets ProjectionLag.HasProgressionRow tell "registered here, never started here" from "at zero".
The generic interface satisfies it from AllShards(), so no store needs to change. The non-generic default throws rather than returning an empty list: an empty registry is a meaningful answer, and handing one back is indistinguishable from "nothing is registered".
The explorer reads were scoped by tenant only. On a store whose DatabaseCardinality is not Single, a store-global read answers from whichever database the default session resolved and looks exactly like a complete answer. New overloads take an IEventDatabase, in the shape FetchProjectionLagAsync and DeleteProjectionProgressAsync already use:
GetRecentStreamsAsync(IEventDatabase, int, string?, CancellationToken)ReadStreamAsync(IEventDatabase, string, string?, CancellationToken)GetStreamMetadataAsync(IEventDatabase, string, string?, CancellationToken)QueryByTagsAsync(IEventDatabase, IReadOnlyDictionary<string, string>, string?, CancellationToken)GetProjectionStatusesAsync(IEventDatabase, string?, CancellationToken)A tool enumerates AllDatabases() and reads each one, attributing the answer to the database it came from. The default delegates on a single-database store (so those are correct with no implementation work), refuses on a multi-database one rather than answering from whichever database it happened to open, and rejects a null database rather than letting it read as "store-global".
Store-side follow-ups — deciding the tenant predicate by tenancy style rather than cardinality, and making a store-global read on a multi-database store fan out or throw — are tracked in JasperFx/marten#5383, JasperFx/polecat#584 and JasperFx/fisher#240.
EventStoreExplorerCompliance gained single-database coverage of the new overloads (skipped unless a store reports exactly one database through AllDatabases()), and AsyncDaemonCompliance asserts RegisteredShardNames() off the non-generic interface.
One column per quarter.