Consume JasperFx 2.1.2 across all JasperFx.* packages#4564
Merged
Conversation
Bump the four JasperFx packages Marten depends on to the aligned 2.1.2 release (they now lock to a single $(JasperFxVersion) upstream): - JasperFx 2.0.1 -> 2.1.2 - JasperFx.Events 2.1.1 -> 2.1.2 - JasperFx.Events.SourceGenerator 2.1.1 -> 2.1.2 - JasperFx.SourceGenerator 2.0.1 -> 2.1.2 JasperFx.RuntimeCompiler is intentionally left alone — it versions independently upstream and is not part of the 2.1.2 set (and master no longer references it). 2.1.2 carries the #4562 event-parameter-naming generator support (accepts `ev` as a conventional event parameter name) whose docs landed in #4563. Full solution builds clean against 2.1.2 (0 errors, all 45 projects); no API adaptation needed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
What
Bumps the four JasperFx packages Marten depends on to the aligned 2.1.2 release (upstream now locks them to a single
$(JasperFxVersion)):JasperFx.RuntimeCompileris intentionally not touched — it versions independently upstream and isn't part of the 2.1.2 set (master no longer references it anyway).Why
2.1.2 carries the #4562 event-parameter-naming generator support (the source generator now accepts
evas a conventional event parameter name acrossSingleStreamProjection/MultiStreamProjection/EventProjection). The documentation for that behavior already landed in #4563; this PR delivers the actual generator via the package bump.Validation
JasperFx2.0.1 → 2.1.2 minor bump.🤖 Generated with Claude Code