Skip to content

fix(ci): regenerate actions.lock to match the SHA-pinned workflows - #273

Closed
hyperpolymath wants to merge 2 commits into
mainfrom
fix/actions-lock-resync
Closed

hyperpolymath wants to merge 2 commits into
mainfrom
fix/actions-lock-resync

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Follow-up to #272. Pinning action refs without regenerating the lockfile makes the whole repo unstartable. gh actions-lock is not in any released gh CLI, so the manifest was regenerated from the workflows.

The lockfile is a manifest of workflow -> action@ref. Pinning the refs without
regenerating it makes the whole repository unstartable:
  Invalid lockfile: .github/workflows/actions.lock#L1 — regenerate with `gh actions-lock`.

`gh actions-lock` is not in any released gh CLI, so this regenerates the manifest
from the workflows themselves, preserving each action's owner_id/repo_id.
@coderabbitai

coderabbitai Bot commented Sep 19, 2026

Copy link
Copy Markdown
Contributor

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@hyperpolymath
hyperpolymath deleted the fix/actions-lock-resync branch September 19, 2026 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant