Bump JasperFx to 2.24.0 (cross-product rebuild cap, jasperfx#498)#4899
Merged
Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XNfeNz73Q3EdiTgSeDbo96
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Consumes JasperFx 2.24.0 — the intra-projection tenant/shard cross-product rebuild cap (#497 / #498, epic #486 WS3 follow-up).
The cap surfaced in #463 was projection-level; #498 extends it into
JasperFxAsyncDaemon's per-(tenant, shard) rebuild fan-out via one shared per-database budget, and — en route — fixed intra-database rebuild replay that had been accidentally serialized at 1. Marten's rebuild path picks this up transparently throughJasperFx.Events.All four JasperFx.* packages lockstepped 2.23.0 → 2.24.0. Marten core + DaemonTests build clean locally.
🤖 Generated with Claude Code