Repository navigation
Grant the release workflow write access to create GitHub releases - #42
Merged
Merged
Conversation
The v0.1.2 tag run failed with 'Resource not accessible by integration' at the create-release step: the default GITHUB_TOKEN is read-only in this repo. Add an explicit permissions block (contents: write) so tauri-action can create the draft release and upload build artifacts. Co-authored-by: setzor <setzor@users.noreply.github.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
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.
Summary
v0.1.2release run failed at the create-release step withResource not accessible by integration: the defaultGITHUB_TOKENis read-only in this repo, sotauri-actioncould not create the draft release or upload artifactspermissions: contents: writeblock to the Release workflow so the tagged-release builds can publishVerification
v0.1.2moved to the merge commit, or a freshv0.1.3) will re-run the release buildsFollow-up needed
v0.1.2tag points at a commit before this fix; to get builds for 0.1.2, delete and re-push the tag after this merges (or I can do it if you confirm)