Potential fix for code scanning alert no. 1816: Workflow does not contain permissions #4918
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/codeharborhub/codeharborhub.github.io/security/code-scanning/1816
To fix the problem, explicitly declare minimal
GITHUB_TOKENpermissions for thebuildjob instead of relying on inherited defaults. Sincebuildonly checks out the code, installs dependencies, and runs tests, it should need at most read access to repository contents. We can therefore setpermissions: contents: readon thebuildjob.Concretely, in
.github/workflows/release-package.yml, add apermissionsblock underjobs.build, at the same indentation level asruns-on. This will mirror the existing pattern used bypublish-gprbut with narrower access. No other steps or jobs need to change, and no additional imports or methods are required because this is a YAML workflow configuration change only.Suggested fixes powered by Copilot Autofix. Review carefully before merging.