Repository navigation
Pin tj-actions/changed-files to a commit SHA - #1200
Merged
Merged
Conversation
The v46 tag is mutable. Pin all three workflows to the v46.0.5 commit (ed68ef8), which is what v46 currently points to, so a moved tag cannot change what runs in CI.
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.
Scope
CI only. No standard, research, or documentation changes.
What changed
The lock, markdownlint, and spell-check workflows used
tj-actions/changed-files@v46, a mutable tag on the action whose tags were repointed to malicious code in March 2025. All three now pined68ef82c095e0d48ec87eccea555d944a631a4c(v46.0.5), the commitv46points to today, so CI behavior does not change.The other actions in use are GitHub's own
actions/checkoutandactions/setup-node.Validation
v46andv46.0.5both resolve toed68ef8intj-actions/changed-files.