Release workflow: create release on the fork, not upstream - #3
Merged
Conversation
GitHub now forces Node 20 actions onto the deprecated Node 24 shim. Pin to the current major releases, which target node24 natively: actions/checkout v4.1.1 -> v7.0.0 actions/upload-artifact v4.0.0 -> v7.0.1 actions/download-artifact v4.3.0 -> v8.0.1 Ref: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/ Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The previous run built all three platforms successfully but the release job failed with: HTTP 403: Resource not accessible by integration (https://api.github.com/repos/bazelbuild/bazel/releases) The "Generate release notes" step adds an `upstream` remote, and an unqualified `gh release create` resolves to the base repo (upstream bazelbuild/bazel) instead of this fork — hence the 403. Pass --repo "$GITHUB_REPOSITORY" so the release is always created here. Also re-applies the Node 24 action pin bump, which was dropped from the PR #2 merge. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Follow-up to #2. The last run (build) built all three platforms successfully (the arm64
lldfix worked 🎉), but the release job failed:Fix
The "Generate release notes" step adds an
upstreamremote (bazelbuild/bazel) to compute drift. An unqualifiedgh release createthen resolves to that base repo rather than this fork, so it tried to publish tobazelbuild/bazel→ 403. Pass--repo "$GITHUB_REPOSITORY"so the release is always created here.Also: re-applies the Node 24 pin bump
The
actions/*→ Node 24 pin bump (last commit of #2) was dropped from #2's merge — master still hadcheckout@v4.1.1etc. This PR re-applies it (checkout v7.0.0,upload-artifact v7.0.1,download-artifact v8.0.1).🤖 Generated with Claude Code