chore(ci): update BCR fork location after move to aspect-forks org - #284
Merged
Conversation
The bazel-central-registry fork moved from aspect-build to aspect-forks. Pushes to the old location succeed via redirect, but the GitHub API does not follow redirects when resolving the PR head ref, so publish-to-bcr fails to open the BCR pull request with 422 'head invalid'. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✨ Aspect Workflows Tasks📅 Wed Jun 3 20:24:37 UTC 2026 ✅ 21 successful tasks
⏱ Last updated Wed Jun 3 20:26:39 UTC 2026 · 📊 GitHub API quota 7,670/15,000 (51% used, resets in 5m, throttle 8×) |
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.
The
bazel-central-registryfork moved fromaspect-buildtoaspect-forks. Pushes to the old location still succeed via git's redirect handling, but the GitHub API does not follow repo redirects when resolving the PRheadref, so publish-to-bcr fails to open the BCR pull request with422 Validation Failed: head invalid.This already broke the rules_js v3.2.0 release publish: https://github.com/aspect-build/rules_js/actions/runs/26905308688/job/79370430005 — every repo pointing
registry_forkat the old location will hit the same failure on its next release.🤖 Generated with Claude Code