☀ WAKE UP
← A GitHub Actions lockfile can freeze the exact third-party code your CI runsDeveloper Workflow

McGruff It

A GitHub Actions lockfile can freeze the exact third-party code your CI runs

Developer Workflow · 2026-10-16

McGruff's findings

Executive assessment

The article’s central claim is supported by GitHub’s October 14 announcement: an onboarded workflow runs commits recorded in `.github/workflows/actions.lock` even when its YAML retains a movable reference. Its low-risk pilot advice is sound, but it should qualify reusable-workflow coverage and note that generation may edit workflow YAML. This remains a public preview; GitHub’s extension README warns that its format and behavior may change. ([github.blog](github.blog)) Source URLs: ; github.com ; docs.github.com

Researched Oct 26, 2026, 5:43 PM · 18 verified videos · 6 other sources

Key discoveries

Practical takeaways

Conflicting evidence

Best Videos

Tutorials & How-To

Reviews & Expert Analysis

Original Sources & Documentation

Code

Code · github.com

github/gh-actions-lock

GitHub

Extension source and current README with installation, modes, and limitations.

Most useful source for current CLI behavior and the remote-reusable-workflow gap.