1min.

1MIN · DEVELOPER TOOLS

A practical guide to locking GitHub Actions dependencies

Hugo van Kemenade shows how to replace long commit hashes in workflow files with readable version tags backed by GitHub Actions lockfiles. The generated file records exact commits and repository identities, including transitive action dependencies. His workflow adds a verification job so stale locks fail CI, while dependency-update tools can maintain the lockfile alongside version changes.

Hugo van Kemenade · Nov 11, 2026

Why it matters

Readable dependency versions can coexist with explicit control over which action code executes.

More context

Install the GitHub CLI’s gh-actions-lock extension, generate a lockfile and review the diff in a small repository. Re-run verification after workflow edits. GitHub’s documentation confirms that reusable workflow calls need their own full-SHA pinning; their internal actions follow the called repository’s lockfile.

Keep in mind

This is a November 11 adoption guide, not a new launch announcement. Locking does not make dependency code trustworthy or pin runner images, secrets and every other build input.

Original read

More engineering ideas, one minute at a time.

Explore more stories