Potential fix for code scanning alert no. 1: Workflow does not contain permissions - #49
Merged
Conversation
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
xiwenc
marked this pull request as ready for review
July 30, 2025 09:59
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/mxlint/mxlint-cli/security/code-scanning/1
To fix the problem, we should add a
permissionsblock to the workflow file.github/workflows/release.yml. This block can be added at the top level (applies to all jobs) or at the job level (applies only to the specific job). Since the workflow only has one job, either location is acceptable, but top-level is preferred for clarity and future extensibility. The minimal starting point iscontents: read, but since the workflow uses a release action, it may needcontents: writeto create or update releases and upload assets. Therefore, setcontents: writeat the workflow level. No other permissions are required unless the workflow interacts with issues or pull requests, which it does not.Required changes:
permissionsblock at the top level of.github/workflows/release.yml(aftername:and beforeon:).contents: writeas the value.Suggested fixes powered by Copilot Autofix. Review carefully before merging.