Repository navigation
Lock GitHub Actions with actions.lock - #467
Draft
stefanvanburen wants to merge 1 commit into
Draft
stefanvanburen wants to merge 1 commit into
stefanvanburen wants to merge 1 commit into
Conversation
Generate `.github/workflows/actions.lock` with `gh actions-lock`, which moves action SHAs out of the workflows into the lockfile, so `uses:` lines name tags again. The lockfile also records each action's owner/repo IDs and locks actions used inside composite actions, which inline SHA pins did not cover. Reusable workflows called from other repositories are not locked yet (github/gh-actions-lock#179), so `add-to-project.yaml` and `pr-title.yaml` keep their inline SHAs. Renovate skips digest pinning only for workflows listed in the lockfile, so `helpers:pinGitHubActionDigests` keeps pinning those two. The new `actions-lock` CI job runs `gh actions-lock --verify`, and a Renovate regex manager tracks the extension version it installs. Signed-off-by: Stefan VanBuren <stefan@vanburen.xyz>
Collaborator
|
Thanks for looking at this - there are definitely some advantages like transitive version pins to a lock file. One thing that made me hesitent is setup-uv doesn't publish floating tags for security reasons (predating locks) which means we will have github-actions version bumps anyways, so this will commonly add yet another renovate bump PR. Not a blocker but I wasn't convinced in going for it. At the minimum if going with this, we should use the broadest floating tag where available (most actions except setup-uv) to reduce version bump PRs outside of lockfile maintenance. |
This branch has not been deployed
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.
Trying out GitHub's workflow lockfiles (went GA a couple weeks ago), mostly after reading https://hugovk.dev/blog/2026/lock-github-actions/. Generated with
gh actions-lockand checked locally withgh actions-lock --verify.Renovate's lockfile support is still marked experimental. A local dry-run of Renovate 44.236.4 looks right (no digest pins proposed for locked workflows, the two reusable-workflow callers still get them), but I haven't seen it actually regenerate
actions.lockin an update PR yet, so I think the first Monday batch after this lands is the real test.Ref: https://github.blog/changelog/2026-10-28-github-actions-workflow-lockfiles-are-generally-available/