Bump JasperFx to 2.57.2 - #4196
Merged
Merged
Conversation
Moves the whole 2.57.x line together -- JasperFx, JasperFx.Events, and the two source generator packages that ship with them. Leaving the generators a patch behind the runtime they generate against is the kind of skew that shows up as a codegen mismatch rather than a restore error. JasperFx.RuntimeCompiler stays at 5.0.0; it is on its own line, as the comment in Directory.Packages.props already says. Verified locally: wolverine.slnx builds clean in Release pinned to net9.0 with 0 warnings -- the check that matters for a JasperFx bump, since a tightening change upstream (a new AOT/trim annotation, a type lift into JasperFx.Events) surfaces as warnings in projects the slim solution omits. CoreTests green (2689 passed, 0 failed). Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Merged
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.
Moves the 2.57.x line from 2.57.1 to 2.57.2:
JasperFxJasperFx.EventsJasperFx.Events.SourceGeneratorJasperFx.SourceGeneratorThe two source generator packages are in because they ship as part of the same line — leaving them a patch behind the runtime they generate against is the kind of skew that surfaces as a codegen mismatch rather than a restore error. Say the word if you'd rather hold them at 2.57.1 and I'll trim the diff.
JasperFx.RuntimeCompilerstays at 5.0.0. It is on its own line, as the comment inDirectory.Packages.propsalready notes.Verification
dotnet build wolverine.slnx -c Release -f net9.0— 0 errors, 0 warnings. This is the check that matters for a JasperFx bump specifically: a tightening change upstream (a new AOT/trim annotation, a type lifted from Marten/Polecat intoJasperFx.Events) shows up as warnings in exactly the projectswolverine_slim.slnxomits, so a clean slim build would prove nothing here.CoreTestsin Release on net9.0 — 2689 passed, 0 failed, 2 skipped.🤖 Generated with Claude Code