Skip to content

chore(ci): pin workflow actions via GitHub Actions lockfile - #462

Merged
fproulx-boostsecurity merged 1 commit into
mainfrom
chore/actions-lockfile
Oct 14, 2026
Merged

fproulx-boostsecurity merged 1 commit into
mainfrom
chore/actions-lockfile

Conversation

@fproulx-boostsecurity

Copy link
Copy Markdown
Contributor

Summary

Adopts the new GitHub Actions workflow lockfile (public preview).

  • Adds .github/workflows/actions.lock, generated with gh actions-lock. For every action it records the resolved commit SHA, owner_id and repo_id, and it covers transitive dependencies too (e.g. upload-pages-artifact → upload-artifact).
  • Workflows now reference version tags (actions/checkout@v6.0.2) instead of inline sha # comment pins.

No behavior change

Every resolved commit in the lockfile matches the SHA that was previously pinned inline. The only visible version differences are stale comments that were wrong before:

  • actions/checkout@de0fac2… was commented # v4 in some files; it is actually v6.0.2
  • actions/setup-go@4a36011… was commented # v5; it is actually v6.4.0
  • github/codeql-action@0499de3… was commented # v3.29.5; the lockfile resolves it as v4.31.2

boostsecurityio/poutine-action@main is still a branch ref, now locked to badd750.

🤖 Generated with Claude Code

Move action pinning from inline commit SHAs to the new
`.github/workflows/actions.lock` generated by `gh actions-lock`.
Workflows now reference version tags; the lockfile records the
resolved commit SHA, owner_id and repo_id for each dependency
(including transitive ones).

All resolved SHAs are unchanged from the previous inline pins.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@fproulx-boostsecurity
fproulx-boostsecurity merged commit fa6dbac into main Oct 14, 2026
10 checks passed
@fproulx-boostsecurity
fproulx-boostsecurity deleted the chore/actions-lockfile branch October 14, 2026 16:27
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