Fix: Pin tj-actions/changed-files to specific commit hash for security #913
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
This PR addresses the security vulnerability in the
tj-actions/changed-filesGitHub Action (CVE-2025-30066). The action was recently compromised, potentially allowing attackers to leak secrets from repositories using this action.Changes
.github/workflows/mypy.ymlto pin thetj-actions/changed-filesaction to a specific commit hash (b2d17c0ca3e4ff20b0ae4b84f93228223b51b8d5) instead of using a version tag (v46.0.1).Security Impact
This change follows GitHub's recommended best practice of pinning actions to specific commit hashes rather than version tags to mitigate against supply chain attacks. The commit hash corresponds to a verified safe version of the action.
References