GitHub Actions workflow dependency lockfiles are in public preview for Free, Team, Enterprise Cloud, and Enterprise Cloud with data residency. According to GitHub, the gh actions-lock extension generates.github/workflows/actions.lock to pin action dependencies to exact commits. These dependencies include transitive actions and reusable workflow references. Teams can adopt locking one workflow at a time. Dependencies inside a reusable workflow use the lockfile in the repository that defines that workflow. Sources: GitHub, GitHub Docs
CloudSource: GitHub
GitHub previews dependency lockfiles for Actions workflows
Why it matters
GitHub says locking preserves selected commits when upstream tags or branches change, but cautions that pinning a commit does not establish its safety. [2] Developers should review the generated diff and check action allowlists. [3]
Attribution
Sources
- 1GitHubGitHub Actions workflow lockfiles in public previewSource published (UTC)
- 2GitHub DocsWorkflow dependency lockfiles
- 3GitHub DocsLocking action dependencies in a repository's workflows
- 4GitHub DocsEnforcing lockfiles for action dependencies
- 5byteiotaGitHub Actions 2026 Security Roadmap: What Changes Now
Read the original source for full details and context.