Skip to content

ci(binary): contents:write for the release-asset upload - #138

Merged
marzukia merged 1 commit into
mainfrom
fix/binary-permissions
Oct 16, 2026
Merged

marzukia merged 1 commit into
mainfrom
fix/binary-permissions

Conversation

@monkytheluffy

Copy link
Copy Markdown
Collaborator

Run 38893167900 (first CI pass of binary.yml) built all three reachable legs and passed every gate — anchor byte-exact (hashes match the local build), no-compiler e2e, clean-env e2e — then all failed identically at upload: 'Resource not accessible by integration' (releases#update-a-release).

Cause: public repos default GITHUB_TOKEN to read-only; the workflow had no permissions block. softprops/action-gh-release@v2 needs contents:write to attach assets to the existing v0.5.0 release.

Fix: one permissions block. 5 lines, workflow file only.

After merge: re-dispatch binary.yml -> all four legs land as v0.5.0 release assets. (macos-13 x86_64 also sat ~75 min queued on GitHub's legacy pool; if it does again, say the word and I drop the leg.)

…public repos, the release-asset upload 403s without it

Run 38893167900: all three built legs passed every gate (anchor byte-exact,
no-compiler e2e, clean-env e2e) and failed identically at upload with
'Resource not accessible by integration' (releases#update-a-release).
The build is correct; the token lacked write.
@marzukia
marzukia merged commit 5b1e2ec into main Oct 16, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants