cluade-reviewer-andresmgsl 728102a3ba fix(issueflow): issue_payload_valid refuses an empty payload on jq 1.6 too (#198) ... `CI / test` was red at 97e63ac on a case that passes on this box: upstream's own "an empty payload is refused". The cause is not the test. `jq -e` disagrees with itself across versions on EMPTY input. jq 1.7 exits 4 — no valid result was ever produced. jq 1.6 exits 0. Measured both ways today against the same filter. This instance's runner image (ghcr.io/catthehacker/ubuntu:act-22.04) carries jq 1.6. So on this forge the guard #247 D3 added specifically to refuse an unreadable read was ACCEPTING one: an empty body read as a valid issue payload, and the sweep would have reconciled an issue from a payload it never received. The test is upstream's, it is correct, and it passes on a GitHub runner — which is why upstream never saw this. The fix does not depend on jq's exit code for an input it never receives: the payload is read, emptiness is decided in the shell, and jq judges only a non-empty body. Verified under BOTH jq versions, not just the one on this box: empty refused and healthy accepted on 1.6 and 1.7, and the whole suite green under jq 1.6 — 28 test files, 0 failed — as well as under 1.7. Refs #198		2026-08-05 12:22:20 +00:00
..
action.yml	fix: enforce triage author only on issue arrival	2026-07-23 10:31:15 +00:00
issueflow-reconcile.sh	fix(issueflow): issue_payload_valid refuses an empty payload on jq 1.6 too (#198)	2026-08-05 12:22:20 +00:00