Skip to content

🔒 ci: lock workflow actions with a lockfile - #67

Merged
gaborbernat merged 2 commits into
mainfrom
actions-lockfile
Nov 10, 2026
Merged

gaborbernat merged 2 commits into
mainfrom
actions-lockfile

Conversation

@gaborbernat

@gaborbernat gaborbernat commented Nov 10, 2026 •

Copy link
Copy Markdown
Member

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. With the lockfile in place, the repository can turn on the Require lockfile Actions policy.

gh-actions-lock wrote .github/workflows/actions.lock and turned step-level SHA pins in the workflows back into tags, which the runner resolves through the lockfile. Reusable workflow calls keep their full SHA, since the lockfile does not cover them.

The published composite action in action.yml keeps its SHA pins, since its users don't get this repository's lockfile. The self-test jobs run that action through uses: $/, and the runner then checks its uses: against this lockfile, so the lockfile records those two dependencies under their SHAs. gh actions-lock would turn the pins back into tags, and how a composite action should lock its own dependencies is still open in gh-actions-lock#183.

@gaborbernat gaborbernat added the skip news No user-facing changelog entry needed label Nov 10, 2026
@gaborbernat
gaborbernat merged commit f42df8c into main Nov 10, 2026
11 checks passed
@gaborbernat
gaborbernat deleted the actions-lockfile branch November 10, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

skip news No user-facing changelog entry needed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant