Potential fix for code scanning alert no. 2: Workflow does not contain permissions #467
Conversation
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
…n permissions Co-authored-by: Copilot Autofix powered by AI <62310815+github-advanced-security[bot]@users.noreply.github.com>
jj22ee
approved these changes
Oct 14, 2025
Contributor
Author
|
Unit Testing / test (py37, ext) (pull_request) failed but has been failing for some time and my changes should not cause this. Bypass |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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/aws/aws-xray-sdk-python/security/code-scanning/2
To fix this problem, an explicit
permissionsblock should be added to the workflow. The permissions should be set to cover only what the workflow actually needs. Foractions/create-release, the minimal required permission is typicallycontents: writeto allow tagging and releasing code. This block can be placed either globally at the workflow root (for all jobs) or specifically within thereleasejob. Here, since there's only one job, adding it at the job level increases clarity about its scope. We will update.github/workflows/Release.yaml, adding apermissions:block withcontents: writeunder thereleasejob definition (right after line 11), and ensure indentation matches the structure.Suggested fixes powered by Copilot Autofix. Review carefully before merging.