Skip to content

ci: lock workflow action dependencies with actions.lock - #79

Merged
rgarcia merged 2 commits into
mainfrom
hypeship/actions-lockfile
Nov 16, 2026
Merged

rgarcia merged 2 commits into
mainfrom
hypeship/actions-lockfile

Conversation

@rgarcia

@rgarcia rgarcia commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

Adds GitHub's workflow dependency lockfile. .github/workflows/actions.lock records the exact commit behind every action the workflows use, and the runner refuses to run an action whose resolved commit doesn't match. A moved or hijacked tag on a third-party action can no longer change what runs in CI.

  • Added .github/workflows/actions.lock, generated with gh actions-lock --no-narrow. No workflow file changes: the generator's uses: lines (actions/checkout@v4, actions/setup-go@v5, actions/create-github-app-token@v1, goreleaser/goreleaser-action@v6.1.0) stay as written, and the lockfile records the commit each one resolves to today.

Not covered: job-level reusable workflow calls (semgrep.yml, vuln-remediation.yml → kernel/security-workflows/...@main). Those are unchanged.

Codegen: ci.yml, release-doctor.yml and publish-release.yml come from Stainless codegen. When codegen changes a uses: line, actions.lock has to be refreshed with gh actions-lock --no-narrow in the same change, or CI/release will fail. Same for advancing a moved v4/v5 tag: gh actions-lock --relock.

  • gh actions-lock --verify passes (all 5 workflows valid).

@rgarcia
rgarcia requested a review from dcruzeneil2 November 13, 2026 21:12

@dcruzeneil2 dcruzeneil2 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approving. This only adds the lockfile, no workflow lines change. Keeping the generated uses: lines as emitted with --no-narrow matches the other generated repos.

What I verified

  • The 4 lockfile entries match the upstream commits and repo/owner ids.
  • gh actions-lock --verify --no-narrow passes locally on this branch.
  • The CI push run on this branch logged "Using locked action versions from the workflow's lockfile" and downloaded checkout and setup-go at the locked SHAs.

@rgarcia
rgarcia merged commit ee30bdd into main Nov 16, 2026
7 checks passed
@rgarcia
rgarcia deleted the hypeship/actions-lockfile branch November 16, 2026 15:00
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.

2 participants