ci: pin zizmor version to avoid random breaks
What changed, and why it matters
This commit changes a GitHub Actions workflow so that a security linting tool called zizmor is installed at a fixed version (1.22.0) instead of the latest release. It is a routine CI maintenance change to prevent unexpected breakages when zizmor releases new versions. There is no indication it fixes or introduces a security vulnerability.
No security action required. This is a CI tooling/version-pinning change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies .github/workflows/zizmor.yml. It renames the job from ‘zizmor latest via PyPI’ to ‘zizmor via PyPI’ and pins the command from ‘uvx zizmor .’ to ‘uvx zizmor@1.22.0 .’. This pins the zizmor static-analysis tool to a specific PyPI version, making CI behavior deterministic. No code, dependency, or workflow security configuration affecting the project runtime is changed.
Changed components
.github/workflows/zizmor.ymlInspect captured patch +2 / −2
diff --git a/.github/workflows/zizmor.yml b/.github/workflows/zizmor.yml
index 0aba6efa..85a0c9a6 100644
--- a/.github/workflows/zizmor.yml
+++ b/.github/workflows/zizmor.yml
@@ -10,7 +10,7 @@ permissions: {}
jobs:
zizmor:
- name: zizmor latest via PyPI
+ name: zizmor via PyPI
runs-on: ubuntu-latest
steps:
- name: Checkout repository
@@ -22,4 +22,4 @@ jobs:
uses: astral-sh/setup-uv@85856786d1ce8acfbcc2f13a5f3fbd6b938f9f41 # v5
- name: Run zizmor 🌈
- run: uvx zizmor .
+ run: uvx zizmor@1.22.0 .
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.