fix: pin GitHub Actions to SHA for supply chain security#8
Conversation
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
SHA-pinning PR reviewCI status: ❌ failing
Pre-existing vs new: No CI runs exist on master to directly compare, but this PR modifies only workflow YAML files — zero Go code changes. The Go test failures ( Bump-vs-pin check:
Not merging. CI is failing (pre-existing on base) and 1 action was bumped. ❌ CI failing ( |
|
❌ CI also failing:
Not merging. |
|
❌ CI failing — pre-existing on base (not introduced by this PR) Failing jobs:
No CI history exists on
Not merging — needs human review for the version bump and pre-existing CI breakage. |
|
❌ CI failing + CI failures:
No prior CI runs exist on Bump detected:
The remaining 3 |
|
Bump-vs-pin analysis:
CI note: |
|
CI workflow was never run before this PR. Assume it was already broken. merging it anyway |
Summary
Pin all GitHub Actions to full commit SHAs for supply chain security.
Actions referenced by tag or branch have been resolved to their commit SHA, with the original ref preserved as an inline comment. Where a sub-action had unpinned transitive dependencies, the action was upgraded to the closest newer version where all sub-actions are fully pinned.
References to this repo's own reusable workflows / composite actions have been rewritten to relative
./paths, which run from the current commit and are exempt from SHA-pinning enforcement.