Potential fix for code scanning alert no. 9: Workflow does not contain permissions #53
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.
Potential fix for https://github.com/bixu/apiary/security/code-scanning/9
To fix the problem, we should add an explicit
permissionsblock to the workflow file, preferably at the top level so it applies to all jobs unless overridden. The minimal set of permissions required should be declared, following the principle of least privilege. For this workflow, which involves managing releases (creating, uploading, publishing), and triggering repository dispatch events, the following permissions are likely required:contents: write(for creating and modifying releases)actions: read(basic action execution)contents: writecovers most needs for release and dispatch.Add the following block after the
name:line and before theon:block:If it turns out you need, for example,
pull-requests: writefor other purposes, you can add that. But for this workflow,contents: writesuffices.Change to be made:
permissions:block at the top of.github/workflows/release.yml, betweenname: Releaseand line 3 (on:).Suggested fixes powered by Copilot Autofix. Review carefully before merging.