From 6b7034a8cd34e2b795958f88525aa43b3c9a2237 Mon Sep 17 00:00:00 2001 From: sudolulo Date: Tue, 14 Jul 2026 03:06:44 +0000 Subject: [PATCH] A change to the publisher did not re-run the check compat.yml's push paths listed tools/compat.py but not tools/compat_publish.py. So the commit that taught the bot to refresh a stale report body fired no run, and the report stayed stale until the next scheduled one -- caught by watching for the run that never came. A fix nobody runs is a fix nobody has. --- .github/workflows/compat.yml | 5 +++++ CHANGELOG.md | 5 +++++ 2 files changed, 10 insertions(+) diff --git a/.github/workflows/compat.yml b/.github/workflows/compat.yml index 593cf66..6ccc3f3 100644 --- a/.github/workflows/compat.yml +++ b/.github/workflows/compat.yml @@ -24,6 +24,11 @@ on: paths: # The manifest itself changed -- re-check immediately rather than waiting a day. - "tools/compat.py" + # ...and so did the thing that PUBLISHES the finding. This was missing, and it + # showed: the commit teaching the bot to refresh a stale report body touched only + # compat_publish.py, so no run fired, and the report stayed stale until the next + # scheduled one. A fix nobody runs is a fix nobody has. + - "tools/compat_publish.py" - ".github/workflows/compat.yml" permissions: diff --git a/CHANGELOG.md b/CHANGELOG.md index 33d96ce..cf750a2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -61,6 +61,11 @@ worse than no alert, because one day it carries a security fix. normalising line endings, so a forge round-tripping `\r\n` does not cause a rewrite every run) and comments remain strictly a changelog of real changes. +- **A change to the publisher did not re-run the check.** `compat.yml`'s `push:` paths + listed `tools/compat.py` but not `tools/compat_publish.py` — so the very commit that + taught the bot to refresh a stale report body triggered no run, and the report stayed + stale until the next scheduled one. A fix nobody runs is a fix nobody has. + - **The compatibility bot filed a new duplicate bug report on every Gitea run.** `find_issue()` skipped pull requests by testing for the *presence* of the `pull_request` key. GitHub omits that key on a plain issue; Gitea sends it as