Originally published on DevToolHub .
GitHub Actions workflow lockfiles went into public preview on October 14, 2026 and became generally available on October 28. The timing is almost funny: GitHub automated the exact workaround this blog told you to do by hand . A GitHub Actions lockfile pins every action in a workflow, plus its transitive dependencies, to a commit you've actually reviewed, so a tag moving after merge can't quietly swap in different code. Here's what .github/workflows/actions.lock locks, how to roll it out without breaking CI, and the limits GitHub documents but the announcements skip.
I haven't run the extension against a real repository for this guide. Everything below comes from GitHub's changelog, GitHub Docs and the gh-actions-lock README as of November 3, 2026, when the extension was at v0.4.1.…