Potential fix for code scanning alert no. 10: Workflow does not contain permissions#1639
Merged
kevinherron merged 1 commit into1.0from Nov 3, 2025
Merged
Potential fix for code scanning alert no. 10: Workflow does not contain permissions#1639kevinherron merged 1 commit into1.0from
kevinherron merged 1 commit into1.0from
Conversation
…in permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@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
1 participant
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/eclipse-milo/milo/security/code-scanning/10
To fix the problem, add an explicit
permissionsblock to the workflow. The recommended minimal starting point iscontents: read, which restricts theGITHUB_TOKENto reading repository content only. If the job or any steps need additional permissions (such as write access to pull requests, releases, or any other GitHub resources), those can be added, but in this case, none of the steps shown require such access—the workflow publishes to Maven Central, installs a GPG key, and runs Maven, all without manipulating or writing GitHub resources.Add the following block directly below the workflow
name(line 1), at the root level in.github/workflows/maven-release.yml:This ensures all jobs in the workflow inherit the read-only permissions for contents, satisfying CodeQL's requirement and adhering to least privilege principles.
Suggested fixes powered by Copilot Autofix. Review carefully before merging.