Originally reported November 14, 2026.
GitHub made workflow dependency lockfiles generally available on October 28, 2026, about two weeks after the feature entered public preview. The feature is available on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team and Free.
A workflow can keep readable Action references such as actions/checkout@v4, while the runner executes the commits recorded in .github/workflows/actions.lock. The lockfile records both direct and transitive dependencies, including those used by composite Actions. This means a later change to a tag or branch reference does not change the code executed by a locked workflow.
Teams can generate and maintain the file with the gh actions-lock GitHub CLI extension and adopt it workflow by workflow. Once a workflow is enrolled, all its dependencies need lockfile entries. The extension also has a validation mode that checks whether the lockfile is current without changing files, allowing teams to use the check in CI. When Dependabot updates an Action in an enrolled workflow, it updates the corresponding lockfile entry in the same pull request. Administrators can enable a “Require lockfile” policy at the repository, organization or enterprise level.
Locking a commit does not establish that it is safe. GitHub advises reviewing dependencies before locking them. Updates—including Dependabot pull requests—remain review points; automatically merging them could put a malicious change into the lockfile.
Source: infoq.cn (originally published 2026-11-14 15:00 UTC+8)