Repository navigation
🔒 ci: lock workflow actions with a lockfile - #257
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every action this repository's workflows run is now locked to a commit through a workflow lockfile, generally available since 2026-10-28. 🔒 A moved or rewritten tag fails the job before any step runs, and the lock also covers the actions those actions call, which a SHA in
uses:never pinned.gh-actions-lock wrote
.github/workflows/actions.lockand turned step-level SHA pins back into tags, which the runner resolves through the lockfile. Reusable workflow calls keep their full SHA, since the lockfile does not cover them, and move to github-workflows 6.8.0, the first release whose own actions are locked.zizmor moves to 1.32.0, which reads the lockfile; 1.31.1 reports each tag as
unpinned-uses. Dependabot keeps updating actions and regenerates the matching lockfile entry in the same pull request.