AI-Assisted Software DevelopmentOct 15, 2026

GitHub Actions workflow lockfiles enter public preview to stop moved tags from changing what runs

GitHub put workflow dependency lockfiles for Actions into public preview on 14 October 2026 for Enterprise Cloud, Team and Free plans. Tags and branches can move after a workflow is reviewed, so a compromised action can slip new code into later runs. A lockfile keeps those references in the workflow but runs the exact commits that were locked, including transitive and reusable-workflow dependencies. The gh actions-lock extension for the GitHub CLI generates.github/workflows/actions.lock, and workflows can be onboarded one at a time. GitHub notes that locking does not make a dependency safe, so review dependencies before locking them.

What it means Pinning by tag has been the weak point in most CI supply-chain incidents. This gives teams commit-level pinning without hand-editing every workflow.

Where it came from GitHub

Back to the Stream