Upgrade Polecat to 5.2.0 (+ JasperFx 2.29.0)#3458
Merged
Merged
Conversation
Bump the Polecat pin floor [5.1.0,6.0.0) -> [5.2.0,6.0.0). Clean restore against the current JasperFx 2.28.0 / Weasel 9.17.0 pins; full wolverine.slnx builds clean in Release. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Polecat 5.2.0 drops the runtime projection-dispatch fallback and depends on JasperFx / JasperFx.Events 2.29.0. With the pin still at 2.28.0, PolecatTests kept the explicitly-referenced 2.28.0 JasperFx.Events.SourceGenerator (its DropDuplicate target strips Polecat's bundled 2.29.0 copy), and the 2.28.0 generator doesn't recognize Polecat 5.2.0's projection model — so it emitted no dispatchers and every projection/aggregate test failed at runtime with InvalidProjectionException "No source-generated dispatcher found". Bump JasperFx, JasperFx.Events, JasperFx.Events.SourceGenerator, and JasperFx.SourceGenerator 2.28.0 -> 2.29.0 (RuntimeCompiler stays on its 5.x line). This is the coordinated critter-stack bump: Marten 9.16.0 also declares JasperFx 2.29.0, so this aligns it too. Weasel 9.17.0 needs only >= 2.24.1. Verified: full wolverine.slnx builds clean in Release; PolecatTests 243/247 pass, 0 failures (was 71 failures). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
jeremydmiller
changed the title
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.
Bumps the Polecat pin floor
[5.1.0,6.0.0)→[5.2.0,6.0.0), plus the coordinated JasperFx family 2.28.0 → 2.29.0 that Polecat 5.2.0 requires.Why the JasperFx bump is needed
Polecat 5.2.0 drops the runtime projection-dispatch fallback and depends on JasperFx / JasperFx.Events 2.29.0. With the pin at 2.28.0, PolecatTests kept the explicitly-referenced 2.28.0
JasperFx.Events.SourceGenerator(itsDropDuplicatetarget strips Polecat's bundled 2.29.0 copy), and the 2.28.0 generator doesn't recognize Polecat 5.2.0's projection model — it emitted no dispatchers, so every projection/aggregate test failed at runtime withInvalidProjectionException: No source-generated dispatcher found(71 failures in the first CI run).Bumping
JasperFx,JasperFx.Events,JasperFx.Events.SourceGenerator,JasperFx.SourceGenerator→ 2.29.0 (RuntimeCompiler stays on its 5.x line) fixes it. This is the coordinated critter-stack move — Marten 9.16.0 (#3457, merged) also declares JasperFx 2.29.0, so this aligns it too. Weasel 9.17.0 needs only>= 2.24.1.Verification
wolverine.slnxbuilds clean in Release (0/0).PolecatTests: 243/247 pass, 0 failures (4 skipped) — was 71 failures.🤖 Generated with Claude Code