Repository navigation
Fork release: build each upstream nightly within minutes - #6
Merged
Merged
Conversation
…lare Worker GitHub cannot notify a fork of upstream releases, npm registry hooks are gone, and scheduled runs in the fork fired a few times a day or not at all. A Worker checks every minute and sends repository_dispatch once per new upstream nightly; pushes to collin/main build directly, and the cron drops to a 6-hour fallback. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Scheduled runs in the fork were unreliable: the hourly cron fired about 6 times a day, then stopped for 16 hours, so three upstream nightlies went unbuilt. GitHub cannot notify a fork when upstream publishes, and npm registry hooks are gone (the endpoint returns 410).
fork/upstream-nightly-watcher/: a Cloudflare Worker that checks every minute and sends onerepository_dispatch(upstream-nightly) per new upstream nightly. It skips a nightly that is already released or already dispatched, which it recognizes by the run title, so a failed build is not redispatched every minute.fork-release.yml: newrepository_dispatchandpush: collin/maintriggers. The cron runs every 6 h as a fallback and retries failed builds. The existing "skip when released" check keeps extra triggers cheap.repository_dispatchonly runs the workflow on the default branch, so the watcher has no effect until this is merged.🤖 Generated with Claude Code