# Does GitHub Actions have a lockfile? What actions.lock pins and where it stands

Yes: workflow lockfiles went generally available on 28 October 2026. What .github/workflows/actions.lock pins, what it leaves to you, and the dated timeline.

By Grant Unwin, published 2026-11-04. Checked against GitHub's documentation on 2026-11-17. The web page: https://www.runners.io/blog/github-actions-lockfile

Yes. GitHub Actions workflow lockfiles became generally available on 28 October 2026, 2 weeks after a public preview began on 14 October, on Enterprise Cloud (including with data residency), Team and Free plans. A file at `.github/workflows/actions.lock`, written by the `gh actions-lock` extension, pins a commit SHA to every action your workflows use, transitive dependencies included, and the locked commit is what runs.

**In short**

- Workflow lockfiles were generally available from 28 October 2026, 2 weeks after the public preview began on 14 October.
- The file is .github/workflows/actions.lock, written by the gh actions-lock extension and never edited by hand.
- It pins a commit SHA to every action, transitive dependencies included, and the locked commit is what runs.
- It does not pin reusable workflow calls, and does not control inputs, secrets or the runner image.
- It is available on Enterprise Cloud, Enterprise Cloud with data residency, Team and Free plans.

Some pages lag its status: the extension’s own README carried a public preview warning until release 0.4.1 on 2 November. This page is the dated record, read from GitHub’s own pages on the date this post was last checked, with what the lockfile covers and what it leaves to you.

## Is the GitHub Actions lockfile still in preview?

No. GitHub moved it to general availability on 28 October 2026. The roadmap that announced it in March described a `dependencies:` section inside the workflow YAML, and what shipped is a separate file instead, so anything written about the March design describes a different form of it. The timeline:

| Date | What happened | Where it is written |
| --- | --- | --- |
| 26 March 2026, revised 30 March | GitHub's security roadmap announces workflow dependency locking as a dependencies: section in workflow YAML, with a preview in 3 to 6 months and general availability at 6 months. | GitHub blog, the 2026 security roadmap |
| 14 October 2026 | Public preview. The design that shipped is a separate file, .github/workflows/actions.lock, written by the gh actions-lock extension. A Require lockfile policy is in preview too. | GitHub changelog, workflow lockfiles in public preview |
| 28 October 2026 | Generally available, with the preview's capabilities, on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team and Free. | GitHub changelog, workflow lockfiles are generally available |
| 2 November 2026 | gh-actions-lock 0.4.1. Its release notes include "Update README to remove public preview warning". | gh-actions-lock releases |
| When this post was last checked | GitHub's concept page says nothing about preview or general availability. The 28 October changelog is the status. | Workflow dependency lockfiles |

## What does actions.lock pin, and what does it not?

| Question | Answer |
| --- | --- |
| Where it lives | .github/workflows/actions.lock, in the repository. |
| Who writes it | gh actions-lock, a GitHub CLI extension. It should never be edited by hand. |
| What it pins | A commit SHA for every action your workflows depend on, including transitive dependencies. |
| What runs | The locked commit. Allowed-actions policies check the locked commit too. |
| Reusable workflow calls (jobs.\<job\_id>.uses) | Not pinned. Pin those by full SHA yourself. |
| Local actions and container images | Not locked, according to the extension's README: a container image without an @sha256: digest only gets a warning. Pin images by digest. |
| Input parameters, secrets and the runner image | Not controlled. |
| Whether a dependency is safe | Not determined: "Locking does not determine whether the dependency itself is safe." |
| The SHA pinning policy | A lockfile satisfies the Require actions to be pinned to a full-length commit SHA policy for onboarded workflows, and GitHub says it supersedes SHA pinning for repositories that adopt it. |
| Dependabot | A version update for an action in an onboarded workflow regenerates the matching lockfile entry in the same pull request. |
| Making it mandatory | Enterprise, organization and repository administrators can turn on the Require lockfile policy. |
| Plans | GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team and Free. |
| Adoption | Per workflow: one at a time or all at once. An onboarded workflow needs a lockfile entry for every dependency. |

The gap that matters most is reusable workflows: a lockfile pins the actions you call, and not the reusable workflows you call. A line such as `uses: your-org/shared/.github/workflows/build.yml@v2` is still a tag, so pin it to a full commit SHA. And a lockfile guards against a dependency changing under you. It does nothing about a dependency that was already bad when you locked it, so review what you lock.

## How do I turn the lockfile on?

Install the extension, run it once, and commit what it writes. These are the commands from the extension’s README, which we copied and did not run, because running them needs a repository we would be changing:

```bash
gh extension install github/gh-actions-lock
gh actions-lock               # onboard or fix: writes .github/workflows/actions.lock
git add .github/workflows/
gh actions-lock --verify      # in CI: the same checks, and nothing is written
gh actions-lock --relock      # move floating refs such as v4 to their current commits
```

The README says to run it again after you add a workflow or change any `uses:` line, and it carries a warning worth repeating: a lockfile change that moves a floating ref back to an older commit is not detected, so read the lockfile’s diff in review, or pin exact tags.

## Does a lockfile replace pinning actions to a SHA?

For a repository that adopts it, GitHub says yes: it calls the lockfile the strongest protection available, and says it supersedes SHA pinning for repositories that adopt it. Your workflow files can keep readable tags such as `actions/checkout@v7` while the locked commit is what runs. Until a workflow is onboarded, and for reusable workflow calls always, the SHA is still the control. The rest of the hardening checklist, including the tj-actions/changed-files compromise, is in our [security hardening post](https://www.runners.io/blog/github-actions-security-hardening), and the choice of where a job runs is a separate decision, covered in [what to ask a third-party runner service](https://www.runners.io/blog/is-a-third-party-github-actions-runner-service-safe). A lockfile guards what a job runs, not the machine it runs on: for that, see [what an ephemeral runner is](https://www.runners.io/blog/what-is-an-ephemeral-github-actions-runner) and [whether self-hosted runners are safe on a public repository](https://www.runners.io/blog/are-self-hosted-runners-safe-on-a-public-repository). Every size we run, with its memory, disk and rate a minute, is on our [managed GitHub Actions runners](https://www.runners.io/runners) page.

## Sources

- [GitHub Actions workflow lockfiles are generally available (GitHub changelog, 28 October 2026)](https://github.blog/changelog/2026-10-28-github-actions-workflow-lockfiles-are-generally-available/)
- [GitHub Actions workflow lockfiles in public preview (GitHub changelog, 14 October 2026)](https://github.blog/changelog/2026-10-14-github-actions-workflow-lockfiles-in-public-preview/)
- [Workflow dependency lockfiles](https://docs.github.com/en/actions/concepts/security/workflow-dependency-lockfiles)
- [What's coming to our GitHub Actions 2026 security roadmap (GitHub blog, 26 March 2026)](https://github.blog/news-insights/product-news/whats-coming-to-our-github-actions-2026-security-roadmap/)
- [github/gh-actions-lock](https://github.com/github/gh-actions-lock)
- [gh-actions-lock releases](https://github.com/github/gh-actions-lock/releases)
- [Secure use reference](https://docs.github.com/en/actions/reference/security/secure-use)

## Frequently asked questions

### Does GitHub Actions have a lockfile?

Yes. A file at .github/workflows/actions.lock, written by the gh actions-lock extension, pins a commit SHA to every action your workflows use, transitive dependencies included. The locked commit is what runs. It became generally available on 28 October 2026.

### Is the GitHub Actions lockfile generally available?

Yes, since 28 October 2026, on GitHub Enterprise Cloud, Enterprise Cloud with data residency, Team and Free. The public preview ran from 14 October. GitHub's concept page itself states no status, so the changelog is the source.

### Does actions.lock pin reusable workflows?

No. GitHub's page says it does not pin calls to reusable workflows, the uses: line of a job, so pin those by full commit SHA yourself. It also does not control input parameters, secrets or the runner image.

### How do I check in CI that actions.lock is current?

Run gh actions-lock --verify, which makes the same checks as a fix run and writes nothing, according to the extension's README. Run gh actions-lock again after you add a workflow or change any uses: line, and review the lockfile's diff.
