Skip to content

ci: adopt GitHub Actions workflow lockfile to satisfy SHA-pinning policy - #11

Open
shmpwk wants to merge 1 commit into
cifrom
claude/github-actions-sha-pinning
Open

shmpwk wants to merge 1 commit into
cifrom
claude/github-actions-sha-pinning

Conversation

@shmpwk

@shmpwk shmpwk commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

Description

Adopt GitHub Actions workflow lockfiles so this repository satisfies the org policy "Require actions to be pinned to a full-length commit SHA". Same change as tier4/pilot-auto.x2#6106.

Pinning each uses: by hand would not be enough: the composite actions we call pull in their own unpinned dependencies (e.g. pre-commit/action@v3.0.1, stefanzweifel/git-auto-commit-action@v7 via autowarefoundation/autoware-github-actions), which per-workflow pins cannot cover. A lockfile pins direct and transitive dependencies, and per the docs it satisfies the SHA-pinning policy for onboarded workflows.

What changed

  • Added .github/workflows/actions.lock, generated by gh actions-lock (machine-generated — do not edit by hand; run gh actions-lock to update).
  • All 1 workflow onboarded. uses: lines keep readable semver refs; the resolved commit lives in the lockfile.

Ref changes

  • actions/checkout@v4 -> actions/checkout@v4.4.0
  • actions/create-github-app-token@v3 -> actions/create-github-app-token@v3.3.0
  • autowarefoundation/autoware-github-actions/set-git-config@v1 -> autowarefoundation/autoware-github-actions/set-git-config@v1.69.1

gh actions-lock narrows refs to the highest matching full semver within the same major (e.g. actions/checkout@v4 → v4.4.0), since full semver tags rarely move. No major-version bumps. --no-narrow would keep the bare @v4 style refs if preferred.

How was this PR tested?

$ gh actions-lock --verify
All 1 workflow valid

Notes for reviewers

Container-image warnings from --verify (runtime-resolved image expressions) are out of scope — lockfiles pin action commits, not container images.

Dependabot regenerates matching lockfile entries in the same PR when it opens action version updates, so no Dependabot config change is needed.

Effects on system behavior

None.

🤖 Generated with Claude Code

Add .github/workflows/actions.lock generated by `gh actions-lock` and
onboard all 1 workflow to it.

The org policy "Require actions to be pinned to a full-length commit SHA"
rejects workflow runs whose actions are not SHA-pinned. Pinning each
`uses:` by hand is not sufficient: the composite actions we call pull in
their own unpinned dependencies (for example pre-commit/action@v3.0.1 and
stefanzweifel/git-auto-commit-action@v7 via
autowarefoundation/autoware-github-actions), which per-workflow pins
cannot cover. The lockfile pins direct and transitive dependencies alike
and satisfies the policy for every onboarded workflow.

Workflow files keep readable semver refs; the lockfile records the commit
each one resolves to. Refs were narrowed to the highest matching full
semver within the same major (e.g. actions/checkout@v4 -> v4.4.0). No
major-version changes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@shmpwk
shmpwk requested a review from Kotakku November 5, 2026 05:51
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