chore(pre-commit): auto-update hooks (1 update(s)) - #7
Closed
github-actions[bot] wants to merge 17 commits into
Closed
github-actions[bot] wants to merge 17 commits into
github-actions[bot] wants to merge 17 commits into
Conversation
…r improved reliability
…mplify remote URL handling
…es and skip repos without tagged releases
…comment preservation
…dle potential errors
Updated 1 pre-commit hook(s)
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
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.
Summary
ColinDaglish ran on 2026-09-10 11:54:29 UTC and updated 1 hook(s).
Workflow run: 34473704778
Changes
zizmor-pre-commit
[MINOR]v1.29.0→v1.30.1Commits (10)
View commit history
Release Notes
Sponsorship is appreciated!
Bug Fixes 🐛🔗
Fixed a bug where zizmor would crash on pre-commit inputs that reference a GitHub URL with an explicit .git suffix (#2363)
Fixed a bug where self-repository auto-fixes were incorrectly marked as "safe" instead of "unsafe" (#2373)
Risks & Notes
Warning
Short Cooldown Period
Some updates have cooldown periods less than 7 days, which may increase vulnerability to supply chain attacks. Longer cooldown periods provide greater stability and more time to detect potential supply chain issues.
Cooldown Periods Applied