Skip to content

fix(ci): pin claude-code-action and socketdev/action to commit SHAs - #9522

Merged
louib merged 1 commit into
masterfrom
inf-2712-pin-third-party-actions
Aug 19, 2026
Merged

fix(ci): pin claude-code-action and socketdev/action to commit SHAs#9522
louib merged 1 commit into
masterfrom
inf-2712-pin-third-party-actions

Conversation

@ralph-bitgo

@ralph-bitgo ralph-bitgo Bot commented Aug 18, 2026

Copy link
Copy Markdown

What

  • Pin anthropics/claude-code-action in .github/workflows/iyarc-prune.yml
    from the floating @v1 tag to its current commit SHA
    (459ad358ae43fea66bfefd0a1f8d840b4b9791fb # v1.0.194).
  • Pin socketdev/action in .github/workflows/ci.yml (4 job steps) from
    the floating @v1 tag to its current commit SHA
    (937f824ec476dfd164d4a4d9995751427b0be143 # v1.3.0).

Both SHAs were verified against the GitHub API to be exactly what the
@v1 tag currently resolves to for each action, so this is a no-op
behavior change — only the ref is now immutable.

Why

Floating tag refs (@v1) for third-party GitHub Actions let the
upstream maintainer silently swap the code that runs in our CI without
any review on our side — a supply-chain risk. This is the
BitGoJS-scoped slice of INF-2710, which tracks migrating all
grandfathered third-party action usages across the org to commit-SHA
pinning.

Test plan

  • CI runs green on this PR (workflow syntax/action resolution is
    exercised automatically by ci.yml running on the PR itself).

Ticket: INF-2712

@linear-code

linear-code Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

INF-2712

@bitgo-ai-agent-dev
bitgo-ai-agent-dev Bot force-pushed the inf-2712-pin-third-party-actions branch from 0c6b7e1 to 4816279 Compare August 18, 2026 20:07
@ralph-bitgo
ralph-bitgo Bot force-pushed the inf-2712-pin-third-party-actions branch from 4816279 to d66cf51 Compare August 18, 2026 20:07
Replace the floating `v1` tag refs for `anthropics/claude-code-action`
(.github/workflows/iyarc-prune.yml) and `socketdev/action`
(.github/workflows/ci.yml, 4 occurrences) with their full 40-character
commit SHAs, each with a trailing version comment for readability.

Floating tags for third-party GitHub Actions let an upstream maintainer
silently change the code that runs in our CI without any review on our
side, which is a supply-chain risk. This is the BitGoJS-scoped migration
tracked by the org-wide effort to eliminate grandfathered third-party
action exceptions in build-system's zizmor policy.

Ticket: INF-2712
Session-Id: 0143b86e-4506-4d4f-aa4c-7e9122639c6f
Task-Id: fb044426-be5d-481c-9782-f7bab6479ea0
@ralph-bitgo
ralph-bitgo Bot force-pushed the inf-2712-pin-third-party-actions branch from d66cf51 to 483215d Compare August 19, 2026 15:27
@bitgo-ai-agent-dev
bitgo-ai-agent-dev Bot force-pushed the inf-2712-pin-third-party-actions branch from 483215d to 7be5cf7 Compare August 19, 2026 15:27
@louib
louib marked this pull request as ready for review August 19, 2026 15:37
@louib
louib requested review from a team as code owners August 19, 2026 15:38
@louib
louib merged commit 91db748 into master Aug 19, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants