GitHub Actions Lockfiles Pin Workflow Dependencies

Engineering teams running GitHub Actions can now record exact commits for their workflow dependencies on Enterprise, Team, and Free plans.

Updated on Nov. 6, 2026 in Job Search

GitHub Actions Lockfiles Pin Workflow Dependencies

GitHub made workflow dependency lockfiles for GitHub Actions generally available on October 28, 2026, letting teams pin the exact commits their workflows run. The feature is available on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team, and Free plans.

Why it matters

Workflows that reference actions by tag or branch can silently pick up changed code, so a compromised action can alter a pipeline without any change to the repository using it. Lockfiles address that gap by recording the commits behind direct and transitive dependencies, which matters for any business whose build and release process depends on third-party actions.

The feature moved from public preview to general availability in two weeks. It is offered across four GitHub plan tiers: Enterprise Cloud, Enterprise Cloud with data residency, Team, and Free.

The players

GitHub

A developer platform owned by Microsoft that hosts source code and runs the Actions automation service used by software teams worldwide.

CircleCI

A continuous integration and delivery platform that manages build pipelines for software teams and uses a central semantic-versioning registry for its orbs.

The details

Once a workflow is onboarded, every dependency needs a lockfile entry, and the gh actions-lock extension for the GitHub CLI generates and maintains that file. A verification mode checks whether the lockfile is current without changing any files, and Dependabot updates the matching entry whenever it opens a version update for an action in an onboarded workflow. Enterprise, organization, and repository admins can enforce the practice with a 'Require lockfile' policy.

Timeline

  1. October 28, 2026: lockfiles become generally available for GitHub Actions.

  2. November 2, 2026: GitHub announces pull_request_target will be blocked by default.

  3. December 2, 2026: the pull_request_target blocking change takes effect by default.

Market Landscape

CircleCI takes a different route, using a central semantic-versioning registry for orbs rather than commit hashes. GitLab supply chain incidents in March 2026 prompted new pipeline policies across the industry, placing GitHub's lockfile release within a broader push toward pinned, verifiable pipeline dependencies.

Engineering and DevOps leads should decide whether to enable the 'Require lockfile' policy across their organizations and review how auto-merged Dependabot updates flow into production. Teams that auto-merge updates will carry any malicious change straight into the lockfile, so review processes should be checked before enforcing the policy.

The takeaway

Lockfiles shift trust from mutable references to exact commits, but only if reviewers examine dependency updates rather than merging them automatically. Operators should calendar the December 2, 2026 pull_request_target change and audit which workflows depend on it.

What happens next

On December 2, 2026, pull_request_target will be blocked by default in GitHub Actions, so teams relying on it should review their workflows before that date.

Further reading

For broader context on how software teams hire for roles tied to pipeline security and developer tooling, see Job Search.

Source note: This article includes information reported by InfoQ.