chore(ci): weekly pin report now proves the sibling watchers are alive (#372) - #383
Merged
Conversation
#372) xmrig-bump.yml and links.yml both fire and both succeed, but nothing made that visible — a scheduled workflow that silently stops looks, from the tracking issue, exactly like one with nothing to report (the sibling repo found exactly this: a watcher that had never once run). tool-bump.yml now queries the latest completed schedule-event run for each via the Actions runs API and adds a liveness table: a failed lookup or zero scheduled runs is UNCHECKED (counts into the existing failed counter, same UNREACHABLE IS NOT CURRENT doctrine as the pin checks); a non-success conclusion or a run older than 16 days renders bold as dead/stale, never as a pass. row() now takes its accumulator by name so the pin table and the new watcher table share the one row-building definition instead of forking it. Adds `actions: read` to the job's scoped permissions for the runs API call.
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.
Closes #372.
The issue's absent-watcher premise didn't hold (xmrig-bump.yml has fired green on schedule every Monday since July), but the follow-up comment on it named the real residue: a scheduled watcher that silently dies looks exactly like one with nothing to report. The weekly pin report now proves the sibling watchers are alive.
xmrig-bump.yml,links.yml), the last completed schedule-event run's date + conclusion.event=scheduleonly — aworkflow_dispatchproves a hand can trigger it, not that cron still fires.row()helper takes its sink by nameref so both tables share the one row definition the file's header insists on.actions: read(the workflow-runs API needs it on the scoped token).What was run:
actionlint1.7.12 on the file: 0 errors.shellcheck --severity=warningandshfmt -i 2 -don all three extracted run blocks: clean.gh apicalls executed live against this repo — both watchers returned timestamp +success; this surfaced and fixed a real bug (gh apisilently switches to POST when-ffields are present;--method GETis now explicit). The zero-scheduled-runs path was exercised against a workflow that has no schedule trigger.🤖 Generated with Claude Code