Skip to content

Fix zizmor code-scanning alerts - #234

Merged
oliverandrich merged 3 commits into
mainfrom
ci/code-scanning-alerts
Oct 27, 2026
Merged

oliverandrich merged 3 commits into
mainfrom
ci/code-scanning-alerts

Conversation

@oliverandrich

@oliverandrich oliverandrich commented Oct 27, 2026 •

Copy link
Copy Markdown
Member

Resolves the three open zizmor code-scanning alerts.

  • release.yml pinned gh-action-pypi-publish to the v1.14.2 SHA with a release/v1.14 branch comment (ref-version-mismatch, alerts 19 and 20). It now pins v1.14.3 with a tag comment.
  • The uv-secure pre-commit hook comes from an archived repository (archived-uses, alert 12). It is replaced by uv-audit from astral-sh/uv-pre-commit 0.13.6. uv-audit checks uv.lock but not the installed uv binary.
  • pre-commit 4.7.0 requires Python 3.11+ and failed to create Python 3.10 hook environments. The hooks and the Lint job now use Python 3.13, and mise.toml pins pre-commit 4.7.0.

zizmor reported ref-version-mismatch on both publish steps. The SHA was
v1.14.2, but the comment named the moving release/v1.14 branch.
release.yml now pins the v1.14.3 SHA with a tag comment.
zizmor reported archived-uses for the uv-secure hook, whose repository
is archived. .pre-commit-config.yaml now runs uv-audit from
uv-pre-commit 0.13.6, which checks uv.lock but not the uv binary.
pre-commit 4.7.0 requires Python 3.11+. It failed to create Python 3.10
hook environments in the Lint job. default_language_version and the
Lint job now use 3.13, and mise.toml pins pre-commit.
@oliverandrich
oliverandrich merged commit eb3ff94 into main Oct 27, 2026
15 checks passed
@oliverandrich
oliverandrich deleted the ci/code-scanning-alerts branch October 27, 2026 19:03
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