News for hackers. Stuff that matters.
Re:Lock Your GitHub Actions by lukasschwab on Wednesday November 11, 2026 @06:03PM (#50460169)
Are there clear reasons to prefer this over just pinning a commit SHA?
Re:Lock Your GitHub Actions by Arbortheus on Wednesday November 11, 2026 @06:58PM (#50460831)
Presumably it’s for the transitive dependencies. You pin action X, but that (third party) action doesn’t correctly pin the SHA of action Y, so you still get owned if the mutable tag gets moved to a compromised commit.

But with a lockfile (I presume, and haven’t checked yet, but otherwise this feature would be useless), direct and indirect dependencies both get pinned.

Re:Lock Your GitHub Actions by esafak on Wednesday November 11, 2026 @08:25PM (#50461771)

     Use the gh actions-lock extension for the GitHub CLI to generate .github/workflows/actions.lock for actions and their transitive dependencies.
https://github.blog/changelog/2026-10-28-github-actions-work...
Re:Lock Your GitHub Actions by ygouzerh on Thursday November 12, 2026 @01:31AM (#50463757)
You can keep the information provided by the version number, and if the maintainer is using real SemVer, it's easier to upgrade.
Re:Lock Your GitHub Actions by akoboldfrying on Thursday November 12, 2026 @07:37AM (#50466282)
> You can keep the information provided by the version number

The old way of just writing this in a comment on the same line seems fine to me -- intuitive and much more concise.

> if the maintainer is using real SemVer, it's easier to upgrade

Could you elaborate on this? I didn't see how yet.