You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci(security): pin all 3rd-party actions to commit SHAs (closes#7091) (#7102)
Per GitHub's security hardening guide for actions:
> Pinning an action to a full length commit SHA is currently the only
> way to use an action as an immutable release.
Tags are mutable. A compromised maintainer could force-push v3 → a
malicious commit that lands silently in our CI on next run. SHA
pinning makes the action immutable until we explicitly update.
7 actions pinned (resolved 2026-05-06 via `git ls-remote`):
codecov/codecov-action@v6 → 57e3a136b779b570ffcdbf80b3bdc90e7fab3de2
docker/build-push-action@v7 → bcafcacb16a39f128d818304e6c9c0c18556b85f
docker/login-action@v4 → 4907a6ddec9925e35a0a9e82d7399ccc52663121
docker/setup-buildx-action@v4 → 4d04d5d9486b7bd6fa91e7baf45bbb4f8b9deedd
dorny/paths-filter@v3 → d1c1ffe0248fe513906c8e24db8ea791d46f8590
orhun/git-cliff-action@v4 → f50e11560dce63f7c33227798f90b924471a88b5
softprops/action-gh-release@v3 → b4309332981a82ec1c5618f44dd2e27cc8bfbfda
11 occurrences across 6 workflows. Trailing `# vX` comment preserves
human-readable version intent for future SHA bumps.
actions/* (first-party, GitHub-maintained) left tag-pinned per common
practice — the supply-chain risk surface is much smaller for those.
Dependabot already covers `github-actions` ecosystem in
`.github/dependabot.yml` — it'll auto-PR SHA updates as new versions
release, using the version comment for changelog inference.
Co-authored-by: t <t@t>
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments