fix: change setup-python action to specific commit #4856
Merged
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
alisonlhart
approved these changes
Dec 3, 2025
ssbarnea
approved these changes
Dec 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
GitHub orgs can enforce the GitHub Actions they use to be referenced through SHA-pinned versions to protect against supply chain attacks. When the setting is enabled, actions can't run if they are incorrectly pinned, or if they use other actions that are incorrectly pinned:
This is the case of
ansible-lint, whereactions/setup-pythonis pinned through a mutable tag. While we could say that theactions/xxxrepos are probably safe considering they are used everywhere, GitHub doesn't allow to opt-out specific repos from the enforcement, so pinning them is necessary as well.