Skip to content

Adopt JasperFx 2.39.2 #5187

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremydmiller merged 1 commit into from
Aug 4, 2026
+14 −6
Merged

Adopt JasperFx 2.39.2 #5187

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 14 additions & 6 deletions Directory.Packages.props
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,21 +194,29 @@
single stream rebuilds run the actual projection instead of silently falling through to
conventional aggregation off the aggregate type; and the projection a scoped wrapper wraps
is validated rather than only the wrapper, so an invalid configuration fails at startup for
every lifetime instead of only Singleton. -->
<PackageVersion Include="JasperFx" Version="2.39.1" />
<PackageVersion Include="JasperFx.Events" Version="2.39.1" />
every lifetime instead of only Singleton.
JasperFx 2.39.2: jasperfx#630 (marten#5167) — the IEventDatabase batched extended-progression
contract now REQUIRES one row per transaction, and ExtendedProgressionWriter flushes each
batch ordered by shard name. A batch amortizes the CONNECTION, never the transaction: a
multi-row statement holds a row lock on every shard in the batch until it commits, so one
slow projection batch on one row stalled every other shard's telemetry on that database
(Marten's side of this is #5186, which does not depend on this bump). The ordering closes
the cross-writer deadlock hazard — the tracker is per-database and shared, and
BuildProjectionDaemonAsync is not cached, so two writers can race over the same rows. -->
<PackageVersion Include="JasperFx" Version="2.39.2" />
<PackageVersion Include="JasperFx.Events" Version="2.39.2" />
<!--
The shared cross-store event sourcing compliance suites (#5116). Source-only package: the
suites compile inside EventSourcingTests so JasperFx's aggregate source generator can bind
Marten's own session types. Marten.Testing needs it too because MartenComplianceFixture,
which closes the seam, lives beside the rest of the harness.
-->
<PackageVersion Include="JasperFx.Events.ComplianceTests" Version="2.39.1" />
<PackageVersion Include="JasperFx.Events.SourceGenerator" Version="2.39.1">
<PackageVersion Include="JasperFx.Events.ComplianceTests" Version="2.39.2" />
<PackageVersion Include="JasperFx.Events.SourceGenerator" Version="2.39.2">
<PrivateAssets>all</PrivateAssets>
<IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
</PackageVersion>
<PackageVersion Include="JasperFx.SourceGenerator" Version="2.39.1" />
<PackageVersion Include="JasperFx.SourceGenerator" Version="2.39.2" />
<PackageVersion Include="Jil" Version="3.0.0-alpha2" />
<PackageVersion Include="Lamar" Version="7.1.1" />
<PackageVersion Include="Lamar.Microsoft.DependencyInjection" Version="15.0.0" />
Expand Down
Loading