Upstream fix is merged; scope the default to releases through 3.3.1 - #1
Merged
Conversation
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.
The README's
## Upstreamsection said the fix was "tracked in" microsoft/jericho#88. That PR merged 2026-08-14 (530fcaf), closing microsoft/jericho#84, so the section now states the merge and — more usefully — the version bound:Stating the bound rather than the release calendar means this text stays correct once Jericho v4.0 ships, and lets a reader check their own install without knowing the release status.
Also retitles one test docstring from "once #88 lands" to "on an engine carrying #88" — same fact, no expiry.
Fast-forwards onto main.
pytest— 92 passed.