ci: disable nightly build-images#456
Merged
Merged
Conversation
The scheduled run checks out stale upstream 'develop' (no .github/images.json) and targets Optimism Labs' registry, which the fork can't access. Image builds for the fork are handled by docker-build-scan.yaml. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
palango
changed the title
piersy
approved these changes
Jun 17, 2026
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.
What
Removes the nightly
schedulecron from the upstreambuild imagesworkflow on the Celo fork. Keptworkflow_dispatchfor manual/upstream parity.Why
The nightly run always fails:
scheduletrigger the checkout forcesref: develop(build-images.yaml:52/:95), but on the forkdevelopis a stale upstream branch that predates the factory image pipeline and has no.github/images.json→ theplanstep fails withConfig file not found: .github/images.json.buildjob publishes to Optimism Labs' registry (oplabs-tools-artifacts, viavars.GCP_PROJECT_ID_OPLABS_TOOLS_ARTIFACTS) — infra the fork has no access to — so it can never succeed here.Image builds for the fork are handled by
docker-build-scan.yaml, which publishes to Celo's own registry.push/pull_requestonly targetdevelop(never pushed to on the fork), so removingschedulestops the only trigger that actually fires.🤖 Generated with Claude Code