Skip to content

Conversation

@ydah
Copy link

@ydah ydah commented Jan 29, 2026

Summary

Pin all GitHub Actions dependencies to their full commit SHAs instead of mutable version tags to mitigate supply chain attacks.

Changes

  • actions/checkout@v6actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8
  • ruby/setup-ruby@v1ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8

Why

Using version tags (e.g., @v6) leaves workflows vulnerable to supply chain attacks, as tags are mutable and can be modified by attackers who gain write access to an action's repository. Pinning to commit SHAs ensures immutable references.

See: CVE-2025-30066

## Summary

Pin all GitHub Actions dependencies to their full commit SHAs instead of mutable version tags to mitigate supply chain attacks.

## Changes

- `actions/checkout@v6` → `actions/checkout@8e8c483db84b4bee98b60c0593521ed34d9990e8`
- `ruby/setup-ruby@v1` → `ruby/setup-ruby@90be1154f987f4dc0fe0dd0feedac9e473aa4ba8`

## Why

Using version tags (e.g., `@v6`) leaves workflows vulnerable to supply chain attacks, as tags are mutable and can be modified by attackers who gain write access to an action's repository. Pinning to commit SHAs ensures immutable references.

See: [CVE-2025-30066](https://www.cve.org/CVERecord?id=CVE-2025-30066)
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.

1 participant