From 6418c07320fa08badda6ae1cb86288d5709a6164 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Pablo=20Guill=C3=A9n?=
 <284438953+PabloCodes7@users.noreply.github.com>
Date: Sun, 19 Jul 2026 09:45:58 +0200
Subject: [PATCH] Widen shipped patchrail range to <0.8.0

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.
---
 action.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/action.yml b/action.yml
index 8802605..4448fff 100644
--- a/action.yml
+++ b/action.yml
@@ -64,7 +64,7 @@ runs:
           # wrong answer. 0.6.0 also reports the runner's own `##[error]` line on an
           # `unknown` verdict, which is the only thing that makes an unclassified run
           # worth annotating at all; `scripts/annotate.py` surfaces it.
-          python -m pip install --quiet "patchrail>=0.6.0,<0.7.0"
+          python -m pip install --quiet "patchrail>=0.6.0,<0.8.0"
         fi
 
     - name: Explain failure and annotate