Repository navigation
Fork release: watchdog for the Cloudflare watcher - #9
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
github-actions
Bot
added
vouch:trusted
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
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.
When the Cloudflare watcher fails (CPU limit, revoked token, Cloudflare outage), nothing tells the owner. Only the 6-hour fallback still builds.
The scheduled run gets a
watchdogjob. It fails when the newest upstream nightly is over an hour old, isn't released, and has noFork release of <tag>dispatch run. GitHub then mails the owner, as it does for every failed run. The build itself still runs. Tested locally against real data: a released tag passes, an undispatched one fails.🤖 Generated with Claude Code