Skip to content

2.100.1 - #1137

Merged
jeremydmiller merged 1 commit into
mainfrom
stoat/nov-5-releases/jfx-2-100-1-release-pr
Nov 5, 2026
Merged

2.100.1#1137
jeremydmiller merged 1 commit into
mainfrom
stoat/nov-5-releases/jfx-2-100-1-release-pr

Conversation

@jeremydmiller

Copy link
Copy Markdown
Member

Bumps JasperFx to 2.100.1, carrying the #1134 fix already on main (#1135). JasperFx.RuntimeCompiler is unchanged since 5.1.0, so it is not bumped. Full CI gates the release; publishing is left to a person.

Fixes #1136

🤖 Generated with Claude Code

Bump JasperFx to 2.100.1. JasperFx.RuntimeCompiler is unchanged since 5.1.0.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@jeremydmiller
jeremydmiller merged commit 0d09228 into main Nov 5, 2026
1 check failed
@jeremydmiller

Copy link
Copy Markdown
Member Author

CI note: this PR was merged (23:44Z) before its build finished. The build then failed on TenantBatchQueueTests.a_composite_member_runs_inside_its_parents_turn_without_queueing (TenantBatchQueueTests.cs:210, queue.Waiting was 1, expected 0). It failed on net9.0 in the first run and on net10.0 in the re-run of the failed jobs, and passed on the other framework each time. So it looks like a flaky race in that test (added with #1130), not something this version bump caused. I did not edit the test. The same commit's main run (42131697282) also shows failure. Worth a follow-up issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Release JasperFx 2.100.1 (#1134: CatchUpAsync can miss a faulted shard)

1 participant