Adopt JasperFx 2.39.4 and compliance wave 5 part 1 - #414
Merged
Conversation
Enrolls the three shared suites that shipped in 2.39.4 (JasperFx/jasperfx#633): fetch_latest_compliance (7), stream_archiving_compliance (6) and event_store_explorer_compliance (6). Polecat's compliance coverage goes from 105 to 124 tests with zero capability gates. No gates are needed because #413 already fixed what they would have covered: the explorer suite found an empty usage.Events collection (#411) and a null StreamMetadata.Tags (#412) while it was being written, and those landed separately so they did not have to wait on a JasperFx release. The two temporary gates were removed from the compliance library before it shipped, so these assertions run unmodified here. The version jump also picks up 2.39.2 and 2.39.3, which had not been adopted yet. Verified on net9.0 against the published packages: 124/124 compliance. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde
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 JasperFx 2.39.1 → 2.39.4 and enrolls the three compliance suites that shipped in it (JasperFx/jasperfx#633).
fetch_latest_compliancestream_archiving_complianceevent_store_explorer_compliancePolecat's compliance coverage goes 105 → 124 tests, zero capability gates.
No gates, because #413 already fixed what this would have gated
The explorer suite found two defects while it was being written — an empty
usage.Eventscollection (#411) and a nullStreamMetadata.Tags(#412). Those were fixed separately in #413 so they could merge on their own schedule rather than waiting behind a JasperFx release.The consequence is that this PR needs no capability gates at all. The two temporary ones that existed during diagnosis were removed from the compliance library before it shipped, so the assertions here run unmodified against Polecat.
Verified
net9.0, against the published 2.39.4 packages: 124/124 compliance and the full Polecat.Tests suite green.
Note on the version jump
2.39.1 → 2.39.4 also picks up 2.39.2 and 2.39.3, which Polecat had not adopted yet. Marten's matching adoption is JasperFx/marten#5190.
🤖 Generated with Claude Code
https://claude.ai/code/session_01VpDCvJcBDZerieJB4JEHde