Widen shipped patchrail range to <0.8.0 (0.7.x is contract-compatible) - #9
Merged
Conversation
PyPI is at 0.7.3 while the action still pinned <0.7.0, so every consumer of @v1 was installing a 0.6.x classifier. The latest-patchrail canary confirms the newest release still emits the ci_result.v1 contract that scripts/annotate.py reads (python_test_failure + guide URL, no 'No classification'), and the fix-guide-slugs pytest passes against it. Move the upper bound one minor deliberately, per the bound-by-minor convention documented in action.yml.
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 action pinned
patchrail>=0.6.0,<0.7.0, but PyPI is already at 0.7.3. Every@v1consumer has been installing a 0.6.x classifier — weeks of fixes and new failure classes never reaching them.The
latest-patchrailcanary is the gate for this move: it runs the realci explain -> annotate.pypath against the newest release. Verified locally that 0.7.3 still emits thepatchrail.ci_result.v1contract annotate.py reads (python_test_failure, confidence 0.95, guidefix/python-test-failure, no "No classification"), andpytest -q(guide slugs / README snippets / no-log path) passes against it — 35 passed.Change: bump the upper bound one minor, respecting the bound-by-minor convention documented inline in
action.yml(>=0.6.0,<0.7.0→>=0.6.0,<0.8.0). Floor stays 0.6.0.test.ymlgreps the spec straight out ofaction.yml, so this is a single source of truth.CI on this PR is the authoritative check: merge only if the full suite — including
latest-patchrailagainst 0.7.3 — is green.