Repository navigation
Release: state the permissions the workflow needs - #5
Merged
Merged
Conversation
Smoke-testing the autorelease chain on bacluc-agent/component-solution-backup showed that the "Release" workflow the action dispatches fails on its own: ##[error]Error 403: Resource not accessible by integration POST /repos/.../releases -> 403 (run 41836068941) That job creates a GitHub release, which needs contents: write, and reads the merged PRs for the changelog, which needs pull-requests: read. Without a permissions key it only works when the repository default happens to be "read and write permissions"; on this fork the default is restricted, so the step was denied. Declaring both permissions makes the release path independent of the repository setting.
Owner
Author
|
Verified as promised: with this merged, the smoke PR #6 produced tag |
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.
Follow-up to #2/#4, found while smoke-testing the full autorelease chain on this fork: the dispatched
Releaseworkflow itself failed with403 Resource not accessible by integrationonPOST /repos/.../releases(run 41836068941) because it has nopermissionskey and this fork's default workflow permissions are restricted.contents: write(create the release) andpull-requests: read(build the changelog from merged PRs) make the release path independent of the repository setting — the same treatment as #4 gave the tag job.Verified by pushing tag
v0.1.2from master after this merge: [pending evidence]