Skip to content

release: fix GITHUB_TOKEN permissions so bundles actually attach - #7

Open
DenizSAHIN570 wants to merge 1 commit into
uurtech:masterfrom
DenizSAHIN570:upstream/release-ci-permissions
Open

DenizSAHIN570 wants to merge 1 commit into
uurtech:masterfrom
DenizSAHIN570:upstream/release-ci-permissions

Conversation

@DenizSAHIN570

Copy link
Copy Markdown

Checked the release history — v0.1.0 through v0.2.1 all only have the macOS dmg attached, even though the workflow builds Linux and Windows too. Turns out GITHUB_TOKEN defaults to read-only on this repo, so the "Attach to release" step fails silently on every platform with Resource not accessible by integration. Only the dmg ever makes it on because that gets uploaded locally via scripts/publish-dmg.sh.

Adds a scoped permissions: contents: write to release.yml. Tested on my fork — tagged a release and all platforms (ubuntu, windows, macos) attached their bundles correctly this time.

GITHUB_TOKEN defaults to read-only, so softprops/action-gh-release@v2's
Attach to release step fails on every platform with "Resource not
accessible by integration". Checked the last several releases on this
repo (v0.1.0 through v0.2.1) - every one only has the macOS dmg attached,
even though the Linux and Windows builds succeed in the same run. This
scopes GITHUB_TOKEN to just what the workflow needs.
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.

1 participant