Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Force running the latest version of zizmor #256

Closed
wants to merge 1 commit into from

Conversation

masklinn
Copy link
Contributor

@masklinn masklinn commented Feb 1, 2025

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.

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.
@masklinn
Copy link
Contributor Author

masklinn commented Feb 1, 2025

After checking a bit more deeply, zizmor does look to properly be updated so this is unnecessary.

@masklinn masklinn closed this Feb 1, 2025
@masklinn masklinn deleted the zizmor-latest branch February 1, 2025 14:01
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