Skip to content

chore: pin GitHub Actions to full-length commit SHAs#855

Open
joshuarli wants to merge 1 commit intomainfrom
pin-gha-actions
Open

chore: pin GitHub Actions to full-length commit SHAs#855
joshuarli wants to merge 1 commit intomainfrom
pin-gha-actions

Conversation

@joshuarli
Copy link
Copy Markdown
Member

Summary

  • Pin all GitHub Actions references in .github/ workflow files to full-length commit SHAs

Generated by devenv pin_gha.

🤖 Generated with Claude Code

Copy link
Copy Markdown

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Fix All in Cursor

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.


- name: Setup pnpm
uses: pnpm/action-setup@v4
uses: pnpm/action-setup@02f6c237bd2518259fed6c71566509edfb3f2b74 # v4
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Inconsistent pnpm/action-setup SHA across workflow files

Low Severity

pnpm/action-setup in merge-jobs.yml is pinned to SHA 02f6c237bd2518259fed6c71566509edfb3f2b74, while all six other workflow files (deploy.yml, eval.yml, release.yml, smoke-tests.yml, test.yml, token-cost.yml) use SHA a7487c7e89a18df4991f7f222e4898a00d66ddda. Both are labeled as v4 but point to different commits, meaning merge-jobs.yml runs a different version of the action than every other workflow.

Additional Locations (1)
Fix in Cursor Fix in Web

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