What changed
GitHub introduced workflow dependency lockfiles in public preview on October 14, 2026, then declared general availability on October 28 for GitHub Free, Team, Enterprise Cloud and Enterprise Cloud with data residency. The gh-actions-lock CLI extension generates .github/workflows/actions.lock, pinning actions and transitive dependencies to exact commits even when readable tags move. Dependabot updates the lockfile when it updates dependencies in an onboarded workflow. Repository, organization and enterprise administrators can enforce Require lockfile policies, and CI can verify lockfile freshness. GitHub says lockfiles prevent unexpected dependency drift but do not establish that a dependency is safe.
Why it matters
The move to GA removes preview status from a practical supply-chain control for build, deployment and release pipelines. Teams can adopt lockfiles gradually and then enforce them without replacing human-readable action references with long SHAs. For smaller teams, this lowers the maintenance cost of transitive pinning and integrates updates into Dependabot. It does not eliminate malicious dependencies, unsafe runtime downloads or excessive GitHub Actions permissions, and migration should still be tested on production-sensitive workflows.
From October preview to general availability
GitHub's October 28 changelog confirms general availability on Free, Team, Enterprise Cloud and Enterprise Cloud with data residency. This supersedes the earlier public-preview status described in the October 14 announcement. Teams should not treat the feature as enterprise-only or as still awaiting GA.
A repository lockfile controls what executes
The GitHub CLI extension gh-actions-lock generates .github/workflows/actions.lock. For each onboarded workflow it records action references and commit SHAs, plus source repository owner and repository IDs to detect unexpected repository identity changes. GitHub Actions runs the locked commit even when a tag or branch moves. Composite-action transitive dependencies are included; reusable workflows are locked as references, but their own transitive actions are covered by the lockfile in the repository defining that reusable workflow.
Adoption is gradual but strict after onboarding
Teams can onboard one workflow at a time. Once a workflow is onboarded, all of its action dependencies must have valid entries. The extension can verify lockfiles without rewriting them, while the Require lockfile policy can be piloted in Evaluate mode before enforcement. An Active policy can block un-onboarded targeted workflows. GitHub recommends reviewing lockfile changes as code and requiring code-owner approval for the file.
Dependabot maintains—but does not start—coverage
Dependabot version-update pull requests regenerate matching lockfile entries for workflows already onboarded. It does not automatically onboard new workflows. Teams adding a new workflow or uses dependency should regenerate and review the lockfile, then verify it in CI. A moved tag or changed repository identity warrants investigation rather than automatically accepting a replacement.
GA operational controls
Use gh actions-lock to generate the lockfile, onboard workflows incrementally and verify that each dependency is locked. Dependabot regenerates matching lockfile entries on version updates to onboarded workflows. Require lockfile policies can enforce adoption at repository, organization and enterprise levels. GitHub's GA notice warns that the lockfile preserves a chosen dependency version, not its trustworthiness; review and least-privilege controls remain essential.
Limits and remaining questions
The current GA announcement names GitHub.com plans, not self-hosted Enterprise Server. Earlier documentation described the extension as pre-1.0; the GA announcement does not establish that every CLI or file-format detail has reached a 1.0 stability guarantee. Verify the exact current CLI behaviour and reusable-workflow dependency scope against GitHub's documentation before enforcing organisation-wide.