Skip to content

chore(deps): Bump JasperFx.Events from 2.101.0 to 3.8.0 - #85

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/JasperFx.Events-3.8.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/nuget/JasperFx.Events-3.8.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor

Updated JasperFx.Events from 2.101.0 to 3.8.0.

Release notes

Sourced from JasperFx.Events's releases.

3.8.0

A source-generated Evolve dispatcher now also applies conventional Apply/Create/ShouldDelete methods inherited from a base class, and command line and TimeSpan parsing use the invariant culture.

  • Evolve dispatcher routes events to conventional methods inherited from a base class (#​1242, #​1241)
  • Command line numbers and TimeSpan fallbacks are read with the invariant culture; .nuke/temp untracked; Nuke telemetry off (#​1240)
  • TimeSpan quantities are parsed with the invariant culture (#​1236)

3.7.1

  • A stop that lands while an agent is loading a page no longer fails catch-up with "The channel has been closed" (#​1231)
  • A rebuild no longer misses an agent start that was still registering, which made the rebuild fail with a duplicate key on the progression row; a start that loses to a rebuild now throws ShardStartException with reason Rebuilding (#​1233)
  • IdentityRebuildCompliance: a document that loads as null counts as not live, whatever LoadExcludesSoftDeletedDocuments says (#​1232)

3.7.0

  • Event-range marks on IEventDatabase (FetchEventRangeMarkAsync, TrySetEventRangeMarkAsync, SetEventRangeMarkAsync), shared by stored-event rewrites and projection backfills (#​1215, #​1222)
  • Stored-event rewrite store seam: IEventStore.SupportsEventRewrites / RewriteStoredEventsAsync, EventRewriteDefinition, and named transforms through EventRegistry.AddRewriteTransform<T> (#​1215)
  • Projection backfill seam: AsyncOptions.SubscribeFromPriorVersionMark, IEventStore.SupportsBackfills / RunBackfillAsync, and EventRegistry.HasJobHost (#​1222)
  • New compliance suites: EventRangeMarkCompliance, EventRewriteCompliance and BackfillCompliance; IdentityRebuildCompliance fixes for conjoined schemas and soft-deleted loads (#​1227)
  • F# output of a C#-targeted assembly leaves the AotRoots companion out (#​1228)
  • StopAllAsync saves the Stopped status (#​1225, #​1226)

Stores that enrol the compliance suites must enrol or excuse the three new ones.

3.6.0

  • Per-identity rebuild for single-stream projections: IProjectionDaemon.RebuildIdentityAsync (#​1201, #​1216)
  • SequentialGuid: lock-free sequential Guids in PostgreSQL or SQL Server order, replacing COMB and Guid.CreateVersion7() (#​1217, #​1221), with a StreamIdGenerator hook for stores
  • IStorageOperations.LastAppendedPosition; LastAppendedSequence is now an obsolete forwarder (#​1218, #​1219)
  • projections --advance works again, StreamState.ColdVersion, and the Compacted<T> marker as a slice's last event (#​1210, #​1211, #​1214)
  • Aspire.Hosting 13.6.5 (GHSA-f7vh-h5g3-7jrh)

See the 3.6.0 section of the migration guide.

3.5.0

  • #​1206 / #​1204: RememberApplicationAssembly opt-out and ResetRememberedApplicationAssembly().
  • #​1207 / #​1203: an optional stream lane on emitted events, .Emits<T>().OnStream<TAggregate>().
  • #​1208 / #​1202: ForTenant on the shared document write operations.
  • #​1209 / #​1205: the projections floor command (show, pin-current, set, clear).
  • #​1212: read-your-writes: EventStorePosition, LastAppendedSequence and IEventStore.WaitForProjectionsAsync (marten#​6004).

3.4.0

Source generator: open generic aggregates and aggregates nested behind private/protected no longer get evolvers that fail to compile (CS0246 / CS0122); they are skipped with the new JFXEVT008 warning (#​1194, #​1195).

3.3.0

What's changed since 3.2.0

⚠️ Behaviour changes

  • #​1191 (closes #​1188): an aggregate whose only parameterless constructor is non-public now runs that constructor.
    • For a private, protected or internal parameterless constructor, the evolver source generator emitted RuntimeHelpers.GetUninitializedObject. The constructor body and every field and property initializer were skipped, so an aggregate written the way Marten 8 allowed could throw NullReferenceException in its own Apply at the first event.
    • The generated file now calls that constructor through a file-scoped [UnsafeAccessor(UnsafeAccessorKind.Constructor)], which runs the body and the initializers as Marten 8 did. It needs no reflection, so it stays trim and Native AOT safe.
    • This changes 3.0–3.2 behaviour: the body of private A() { ... } runs again.
    • GetUninitializedObject is still used for aggregates with no parameterless constructor at all, such as records with a primary constructor. It is also used for generic aggregates and for aggregates nested inside a private or protected type, because the generated code can't reach their constructors.
  • #​1192 (closes #​1189): non-string [FromKeyedServices] keys resolve the registration with that key.
    • Code generation turned the key into a string before looking it up. An enum key such as [FromKeyedServices(Kind.A)] therefore never matched the registration keyed by Kind.A, and codegen silently injected the last unkeyed registration of the same type.
    • Every codegen path now matches keys the same way: an exact object.Equals match first, as Microsoft.Extensions.DependencyInjection does, then the old ToString() comparison. The generated constructor attribute keeps the key's own type, for example [FromKeyedServices(MyApp.Kind.A)] instead of ("A"). ServiceContainer.QuickBuild resolves with the key as declared.
    • A [FromKeyedServices(key)] parameter with no registration for that key now fails during code generation with an error that names the parameter, the key and the service type. Before, it quietly took the unkeyed default. A null key is still resolved like any other parameter.
    • IServiceVariableSource gains TryFindKeyedService(Type, object key, out Variable?) as a default member. The default handles string keys and throws NotSupportedException for any other key.

Additions

  • #​1190 (closes #​1187): IEventBinarySerializer span and buffer-writer members, so stores can pool binary event buffers (JasperFx/marten#​5731).
    • Adds Serialize(Type, object, IBufferWriter<byte>) and Deserialize(Type, ReadOnlySpan<byte>).
    • Both are default members that fall back to the existing byte[] pair, so serializers written against 3.2 keep working unchanged.
    • Serializers built on System.Text.Json, MessagePack or MemoryPack can override them and stop allocating.
  • #​1186: UnArchiveStream on IEventStoreOperations (marten#​5476).
    • UnArchiveStream(Guid) and UnArchiveStream(string) are now on the shared operations interface, so store-agnostic code can call what ArchivedStreamException tells it to.
    • They are default members that throw NotSupportedException until a store implements them.
    • StreamArchivingCompliance gains unarchive facts. The EventStoreComplianceFixture.UnArchiveStream hook is [Obsolete].

Follow-ups for the stores

  • Marten:
    • Relax the 9.0 migration-guide row about private constructors and field initializers.
    • Drop the workaround in inline_aggregation_with_private_constructor (JasperFx/marten#​5907).
  • Polecat and Fisher: relax the same migration-guide rows if they have them.
  • Marten, Polecat and Fisher: switch the binary event column path to the new IEventBinarySerializer members.

Full Changelog: JasperFx/jasperfx@v3.2.0...v3.3.0

3.2.0

What's changed since 3.1.0

  • #​1185 (closes #​1184): a [BoundaryAggregate] with an Id member now works with FetchForWritingByTags<T>.
    • The source generator used to key such an aggregate's evolver only on its Id type, for example <T, Guid>. Marten fetches every boundary aggregate as SingleStreamProjection<T, string>, so the fetch threw "No source-generated dispatcher found".
    • The generator now also emits the string-keyed evolver. The Id-keyed one stays for single-stream use.
    • "No source-generated dispatcher found" now names the identity type it did find an evolver for. It no longer says the generator "declined" the type.
  • #​1183: DcbAppendConditionCompliance, a shared compliance suite for the DCB append condition under real concurrency (marten#​5887). Adds ComplianceStoreConfig.DisableWriteRetries. Every store's ComplianceSuiteInventory guard needs the new suite enrolled or excused.

Full Changelog: JasperFx/jasperfx@v3.1.0...v3.2.0

3.1.0

What's changed since 3.0.1

  • Runtime-async is on by default for net11.0 (#​1180, #​1182).
    • The net11.0 assemblies compile with runtime-async=on. Opt out with -p:JasperFxRuntimeAsync=false.
    • GenerationRules.UseRuntimeAsync defaults to true in the net11.0 build. Opt out with UseRuntimeAsync = false.
    • net10.0 is unchanged.
    • Watch for: stack traces, debugger stepping, and APM agents or profilers that hook async state machines.
  • AddJasperFx(services, configure, registeredFrom) (#​1179, #​1181): an entry point that defers AddJasperFx into Build() can hand over the assembly it captured, so ApplicationAssemblyReuseWarning no longer fires on a healthy host built by a helper in another assembly.
  • StreamLockedException.StreamIds (#​1172, #​1176): a store whose lock covers several streams can report every stream that lost it.
  • --log-level and --verbose win over configured log levels (#​1132, #​1177).

See "Key Changes in 3.1.0" in the migration guide.

3.0.1

What's Changed

Full Changelog: JasperFx/jasperfx@v2.102.0...v3.0.1

3.0.0-alpha.1

What's Changed

Full Changelog: JasperFx/jasperfx@v2.102.0...v3.0.0-alpha.1

2.102.0

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).
    • Why: a backlog counted in events says little on a multi-tenant fleet. 40,000 events spread over 130 tenants is fine; 40,000 on one tenant for an hour is not. The age of the oldest event a shard hasn't processed tells those two apart, and it's the number an SLO is written against. CritterWatch reaches event stores only through the JasperFx.Events abstractions, so the question has to be answerable here.
    • What it answers: for each (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.
    • Tenants: a null tenant considers every event in the database. A non-null tenant considers only that tenant's events under conjoined tenancy or per-tenant partitioning.
    • Archived events don't count. The async daemon skips them, so a shard is never waiting on one.
    • Cost: stores answer the whole list in one round trip per database, with one sequence seek per position, never a scan or a count. Ask only about shards that are behind.
    • Default implementations: the batched member throws 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.
  • Compliance: a new 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.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.1...v2.102.0

2.101.1

JasperFx 2.101.1 is a patch release with one fix.

  • Overlapping StopAsync / PauseAsync calls on the projection coordinator no longer throw ObjectDisposedException (#​1148 / #​1149).
    • What was broken: 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.
    • When it happened: JasperFx's 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.
    • How it works now: start, pause and stop are serialized, so overlapping calls behave like sequential ones: the first stop tears down and the rest find nothing left to do. Marten's and Polecat's ProjectionCoordinator pick this up from the base class. Marten's ExplicitProjectionCoordinator has its own fix in JasperFx/marten#​5843.
  • CI: concurrency stress tests now live in a separate StressTests project that runs its tests one at a time, so they can't starve timing-sensitive tests of thread-pool threads.

What's Changed

Full Changelog: JasperFx/jasperfx@v2.101.0...v2.101.1

Commits viewable in compare view.

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

---
updated-dependencies:
- dependency-name: JasperFx.Events
  dependency-version: 3.8.0
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants