Skip to content

ci: pin shared workflow/action refs to a commit SHA - #197

Open
SashaMIT wants to merge 1 commit into
aave-dao:mainfrom
SashaMIT:ci/pin-shared-workflow-refs
Open

ci: pin shared workflow/action refs to a commit SHA#197
SashaMIT wants to merge 1 commit into
aave-dao:mainfrom
SashaMIT:ci/pin-shared-workflow-refs

Conversation

@SashaMIT

@SashaMIT SashaMIT commented Aug 6, 2026

Copy link
Copy Markdown

Summary

release.yml grants id-token: write (npm OIDC trusted publishing) and contents: write, but consumes aave-dao/github-workflows/.github/actions/setup-node@main, a mutable branch ref. If the shared repo's main is compromised or a bad commit lands, it flows straight into the publish path that can ship npm packages under the Aave name. GitHub's security hardening guidance recommends pinning third-party (and shared-org) actions to a full-length commit SHA.

Changes

Pin all four aave-dao/github-workflows refs (release.yml, test.yml x2, comment.yml) to the current main commit c6fd9ab, each tagged with a # main comment so the intended branch stays readable.

Test plan

  • All three workflow files still parse as valid YAML
  • Refs resolve: c6fd9ab is the current head of aave-dao/github-workflows@main

Made with Cursor

The release job holds npm OIDC trusted-publishing rights (id-token:
write) and contents: write, but consumes shared actions via the mutable
@main branch ref. A compromised or mistakenly-pushed main on
aave-dao/github-workflows would flow straight into the publish path.

Pin all four aave-dao/github-workflows refs to the current main commit
(c6fd9ab), tagged with a '# main' comment for readability.

Made-with: Cursor
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