GitHub made workflow dependency lockfiles generally available on October 28, 2026, following a public preview roughly two weeks earlier, according to InfoQ’s November 14 report.
A workflow can keep readable references such as actions/checkout@v4, while its runner executes the commits recorded in .github/workflows/actions.lock. The lockfile records commits for both direct and transitive dependencies, including dependencies used by composite Actions. This helps prevent a later change to a tag or branch from silently changing the code a workflow runs.
Teams can generate and maintain the file with the GitHub CLI’s gh actions-lock extension. Once a workflow adopts lockfiles, its dependencies need corresponding lockfile entries. A validation mode checks whether the file is current without changing files, and teams can migrate workflows gradually. When Dependabot updates an Action in an opted-in workflow, GitHub says it updates the lockfile entry in the same pull request without additional configuration. Enterprise, organization and repository administrators can also enable a Require lockfile policy.
The feature is available on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team and Free. A locked commit is not necessarily a safe commit: GitHub advises reviewing dependencies before locking them. The same review matters when approving Dependabot updates; automatically merging them could lock in a malicious change.
InfoQ also reported that a separate GitHub announcement on November 2, 2026 said pull_request_target would be blocked by default starting December 2, 2026. That was a forthcoming default change at the time of the report, not part of the lockfile release.
Source: infoq.cn (originally published 2026-11-14 15:00 UTC+8)