Force running the latest version of zizmor #256
Closed
Conversation
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
Apparently when restoring the uv cache we might end up running an old release of zizmor, which means we don't get the latest checks. That does avoid getting new failures in a random PR, but it's an annoyance wrt keeping the project progressing.
Contributor
Author
|
After checking a bit more deeply, zizmor does look to properly be updated so this is unnecessary. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Apparently when restoring the uv cache we might end up running an old release of zizmor, which means we don't get the latest checks.
That does avoid getting new failures in a random PR, but it's an annoyance wrt keeping the project progressing.