ci: make a clean maintenance-watch run show its work - #131
Merged
Conversation
The first run printed "Nothing outstanding" and nothing else. That was the correct answer, but the output is indistinguishable from a run whose checks silently did nothing — which is the exact failure this workflow was added to replace, and the same shape as a nightly that goes green because a broken package aged out of its window. Now every run logs what it examined: how many open PRs, how many of the last seven scheduled registry runs failed and the latest result, and the local version against npm. An all-clear is auditable instead of asserted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NBQQpA86yYzwJUiVz8ph2R
|
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
2 participants
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.
Summary
The first run of
maintenance-watch(dispatched right after #130 merged) printed:That was the correct answer — I checked each condition by hand afterwards:
package.jsonis 1.2.3 and npm latest is 1.2.3But the output proves none of that. It's indistinguishable from a run whose checks silently did nothing — which is exactly the failure this workflow was added to replace, and the same shape as a nightly that goes green because a broken package aged out of
--since.Change
Every run now logs what it examined:
An all-clear becomes auditable instead of asserted. If a future run reports
Examined 0 open PR(s)while PRs are visibly open, that's a bug you can see rather than silence you have to trust.Test plan
runblocks passbash -nWill dispatch once merged, same as #130, and confirm the line appears with real numbers.
Generated by Claude Code