Repository navigation
ci: pin tj-actions/changed-files to v46.0.1 SHA (GHSA-mrrh-fwg8-r2c3) - #521
Merged
Merged
Conversation
Pin tj-actions/changed-files to the v46.0.1 commit SHA instead of the mutable v44 tag. The tag was re-pointed to a malicious commit in March 2025 (CVE-2025-30066). No input/output changes affect automerge.yml. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Summary
.github/workflows/automerge.ymlreferencedtj-actions/changed-files@v44, a mutable tag. This PR pins it to the commit forv46.0.1(2f7c5bfce28377bc069a65ba478de0a74aa0ca32).Why
GHSA-mrrh-fwg8-r2c3 / CVE-2025-30066: in March 2025 the tags of
tj-actions/changed-fileswere re-pointed to a malicious commit (0e58ed8671d6b60d0890c21b07f8835ace038e67) that printed CI runner secrets into workflow logs. Because we followed a mutable tag, a tag move alone would have changed the code we run. Pinning to a full commit SHA prevents that. The same pin is already used in seamapi/docs.Verification
gh api repos/tj-actions/changed-files/git/ref/tags/v46.0.1resolves to2f7c5bfce28377bc069a65ba478de0a74aa0ca32, which is the pinned SHA.0e58ed86….Compatibility (v44 to v46.0.1)
No change needed to
automerge.yml.action.yml(inputs, outputs,runs.using: node20) is byte-for-byte identical between v44.5.7 and the pinned SHA, and this workflow only uses thefilesinput and theany_changedoutput. The v45 and v46 release notes list dependency bumps and docs/security notices only. This job only runs for Dependabot (or seambot) PRs, so it will not run on this PR; the first such PR after merge is the real test.Release
The commit type is
ci:..releaserc.jsonuses only@semantic-release/commit-analyzerwith the default preset, under whichci:does not produce a release.Other third-party actions still on mutable tags (not changed here)
DamianReeves/write-file-action@v1.3balvajs/delete-stale-branches@v2crazy-max/ghaction-import-gpg@v7cycjimmy/semantic-release-action@v6fountainhead/action-wait-for-check@v1.2.0shivammathur/setup-php@v2softprops/action-gh-release@v3stefanzweifel/git-auto-commit-action@v7Consider pinning these to SHAs as follow-up.
🤖 Generated with Claude Code