devsyncwrldandClaude Opus 5
293378293d
CI / Build & test (Node 20) (push) Canceled after 0s
CI / Build & test (Node 24) (push) Canceled after 0s
CI / Build & test (push) Canceled after 0s
CodeQL / Analyze (javascript-typescript) (push) Canceled after 0s
Security / Secret scan (gitleaks) (push) Canceled after 0s
Security / Dependency scan (OSV-Scanner) (push) Canceled after 0s
Security / IaC/config scan (Trivy) (push) Canceled after 0s
Security / License compliance scan (Trivy) (push) Canceled after 0s
OpenSSF Scorecard / Scorecard analysis (push) Canceled after 0s
Two defects, both mine, and the second hid the first. The cleanup built a regex and matched it against the jq line '<id> <name>', so the anchor in latest.yml could never match — it sits after the id. Only the .exe was removed, and each publish left another latest.yml behind. Gitea then served the older one, so the updater kept reporting the previous version as current: an update that exists and is never offered, with nothing logged anywhere. Filtering now happens inside jq, comparing the name directly. The guard meant to catch exactly that was missing its closing fi, so the step died on a syntax error before reaching it. Verified with bash -n this time, which is what should have happened before it ever ran on a runner. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>