Repository navigation
Conversation
Since v0.7.0, zizmor-action installs zizmor by downloading a hash-pinned wheel from PyPI instead of pulling a container image from ghcr.io. This workflow is still on v0.6.4, which pulls the container image. Bumping the action without changing the harden-runner egress allowlist would break the job, because pip can't reach PyPI under the block policy, so both change together. Allow pypi.org and files.pythonhosted.org, drop the container registry endpoints that are no longer used, and bump the action to v0.8.0. This matches chainguard-dev/actions#1134. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cpanato
approved these changes
Nov 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since v0.7.0, zizmor-action installs zizmor by downloading a hash-pinned
wheel from PyPI instead of pulling a container image from ghcr.io.
This workflow is still on v0.6.4, which pulls the container image.
Bumping the action without changing the harden-runner egress allowlist
would break the job, because pip can't reach PyPI under the block
policy, so both change together.
Allow pypi.org and files.pythonhosted.org, drop the container registry
endpoints that are no longer used, and bump the action to v0.8.0. This
matches chainguard-dev/actions#1134.
🤖 Generated with Claude Code