Skip to content

[CI] Pin smoke.yml actions to commit SHAs and name the build job - #435

Merged
Garra1980 merged 1 commit into
mainfrom
Garra1980/zizmor-smoke-yml
Oct 20, 2026
Merged

Garra1980 merged 1 commit into
mainfrom
Garra1980/zizmor-smoke-yml

Conversation

@Garra1980

Copy link
Copy Markdown
Contributor

Summary

Fix all zizmor findings in .github/workflows/smoke.yml.

zizmor 1.30.1 reports 8 findings on the current workflow:

Audit Severity Location
unpinned-uses high actions/checkout@v7 (line 29)
unpinned-uses high actions/cache/restore@v6 (lines 73, 79, 114)
unpinned-uses high actions/cache/save@v6 (lines 102, 108, 128)
anonymous-definition info job build (line 17)

A tag such as v7 can be moved to different code at any time, while a commit SHA cannot.

Changes

  • Pin every action to the commit its major tag points to today:

    • actions/checkout@v7 → 3d3c42e5aac5ba805825da76410c181273ba90b1 (v7.0.1)
    • actions/cache/{restore,save}@v6 → 55cc8345863c7cc4c66a329aec7e433d2d1c52a9 (v6.1.0)

    Each pin keeps the version in a trailing comment, so the existing Dependabot github-actions config keeps proposing updates.

  • Name the job Build and smoke test.

The workflow runs exactly the same action code as before. The parsed workflow is identical to the original apart from the pinned refs and the job name.

Testing

  • zizmor --persona=pedantic .github/workflows/smoke.yml (offline and with a GitHub token): no findings.
  • The CI run on this PR exercises the pinned actions.

🤖 Generated with Claude Code

zizmor 1.30.1 reports unpinned-uses (high) for actions/checkout@v7 and the
six actions/cache/{restore,save}@v6 steps, plus anonymous-definition (info)
for the build job. Pin each action to the commit its major tag points to
today, keeping the version in a trailing comment so Dependabot can keep
bumping it, and give the job a name. zizmor --persona=pedantic now reports
no findings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Garra1980
Garra1980 merged commit a136301 into main Oct 20, 2026
3 checks passed
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