News for hackers. Stuff that matters.
Re:Lock Your GitHub Actions by aleaph on Wednesday November 11, 2026 @06:22PM (#50460400)
So "SHA pinning with version reference in a comment" with extra steps, got it
Re:Lock Your GitHub Actions by OptionOfT on Wednesday November 11, 2026 @06:30PM (#50460494)
Enforced through GitHub Actions that is :)
Re:Lock Your GitHub Actions by sleepytimetea on Wednesday November 11, 2026 @08:46PM (#50461950)
Yes, I scratched my head trying to understand what this accomplishes. It just puts a tag back instead of a SHA but now moves the SHA (locked in) to a separate file that now needs to be verified ? I fail to see how this is better or needed.
Re:Lock Your GitHub Actions by hobofan on Thursday November 12, 2026 @12:22AM (#50463364)
You can still use the SHA if you want to. What it achieves is transitive pinning (which this post doesn't properly highlight).

Lack of transitive pinning support was the biggest supply-chain security criticism against GHA and I'm glad they are finally tackling it!

Re:Lock Your GitHub Actions by edelbitter on Wednesday November 11, 2026 @09:28PM (#50462309)
[delayed]