A release workflow can be reviewed, approved and committed while one of the names it depends on still points to code that may change later. The file in your repository is stable. The thing it refers to may not be.
On 14 October 2026, GitHub announced public preview of workflow dependency lockfiles for Actions. The feature records exact revisions for supported action and reusable-workflow dependencies while allowing readable references in the workflow. GitHub explicitly notes that locking a dependency does not determine whether the locked code is safe. Source: GitHub changelog.
Immutability and safety answer different questions
Our analysis separates two claims. The first is that a later run uses the same reviewed revision. The second is that the reviewed revision is appropriate to execute. A lockfile can help with the first; it cannot settle the second by itself.
That distinction matters because build workflows can have access to sensitive resources. Consistent execution is valuable, but consistently executing an unsuitable dependency is still a problem. The review of the dependency and the record of its identity belong together.
Look beyond the visible workflow file
Imagine a fictional team building a browser extension. Its release workflow calls a reusable workflow that, in turn, depends on other actions. A reviewer looking only at the top-level file may not see every component involved in the final run.
The useful question is which revisions are actually selected across that dependency structure. Teams evaluating the preview should consult the current documentation for the dependencies and workflow patterns it supports, rather than assuming every external input is automatically covered.
A lockfile is part of the evidence about execution. It should be reviewed as a meaningful change, not treated as generated noise that nobody needs to inspect.
Updates need a deliberate review path
Locking code should not become a reason to stop updating it. A fixed revision may later need replacement because of a defect, a security finding or a compatibility change.
A useful update review connects the new revision with the reason for adopting it. Look at the relevant change, check the permissions required by the workflow and run the validation appropriate to the release process.
If a dependency is updated automatically, the generated change still needs an accountable review. Automation can prepare the revision record; it should not make the organization's judgment invisible.
Treat the preview as something to evaluate
Preview status is relevant. Confirm current availability and limitations, then examine a suitable workflow before expanding reliance. A controlled evaluation should include both a normal run and the behavior when a dependency does not match the expected record.
- Inventory the actions and reusable workflows involved.
- Identify references that can move.
- Review locked revisions and the reason for changes.
- Keep an update process alongside the lock.
The broader lesson is easy to miss: an unchanged configuration file does not always imply unchanged execution. This preview gives teams another way to make that hidden dependency visible and keep the code they run connected to the code they reviewed.



