Bump prek from 0.4.5 to 0.4.11

[dependabot]

Bumps prek from 0.4.5 to 0.4.11.

Release notes

Sourced from prek's releases.

0.4.11

Release Notes

Released on 2026-07-25.

Highlights

• This release adds two new builtin hooks, deny-pattern and require-pattern, as native alternatives for pygrep use cases. deny-pattern fails when a configured pattern is found, while require-pattern ensures every selected file contains a match. By matching natively without spawning a Python subprocess, they run over 4x faster than pygrep in benchmarks. Note that they use Rust regex syntax, which does not support look-around features such as negative lookbehind.

• prek run now supports --glob <PATTERN> to run hooks on tracked files matching a glob. It can be repeated or combined with --files and --directory.

• Hook priorities now support reusable aliases:

  [priorities]
  checks = 10
  [[repos]]
  repo = "builtin"
  hooks = [
  { id = "check-json", priority = "checks" },
  { id = "check-yaml", priority = "checks" },
  ]

  This makes parallel scheduling easier to read and maintain.

Enhancements

• Add deny-pattern and require-pattern builtin hooks (#2359)
• Support --glob patterns in prek run (#2381)
• Support reusable aliases for hook priorities (#2331)
• Implement requirements-txt-fixer as a builtin hook (#2390)
• Improve user-facing warnings and errors (#2380)
• Install Node hooks through git url (#2394)

Performance

• Reduce blocking-pool overhead in file hooks (#2384)
• Speed up mixed-line-ending scans with memchr2 (#2391)

Bug fixes

... (truncated)

Changelog

Sourced from prek's changelog.

0.4.11

Released on 2026-07-25.

Highlights

• This release adds two new builtin hooks, deny-pattern and require-pattern, as native alternatives for pygrep use cases. deny-pattern fails when a configured pattern is found, while require-pattern ensures every selected file contains a match. By matching natively without spawning a Python subprocess, they run over 4x faster than pygrep in benchmarks. Note that they use Rust regex syntax, which does not support look-around features such as negative lookbehind.

• prek run now supports --glob <PATTERN> to run hooks on tracked files matching a glob. It can be repeated or combined with --files and --directory.

• Hook priorities now support reusable aliases:

  [priorities]
  checks = 10
  [[repos]]
  repo = "builtin"
  hooks = [
  { id = "check-json", priority = "checks" },
  { id = "check-yaml", priority = "checks" },
  ]

  This makes parallel scheduling easier to read and maintain.

Enhancements

• Add deny-pattern and require-pattern builtin hooks (#2359)
• Support --glob patterns in prek run (#2381)
• Support reusable aliases for hook priorities (#2331)
• Implement requirements-txt-fixer as a builtin hook (#2390)
• Improve user-facing warnings and errors (#2380)
• Install Node hooks through git url (#2394)

Performance

• Reduce blocking-pool overhead in file hooks (#2384)
• Speed up mixed-line-ending scans with memchr2 (#2391)

Bug fixes

... (truncated)

Commits

• 92ba6c8 Bump version to 0.4.11 (#2402)
• f575e42 Bump quinn-proto from 0.11.14 to 0.11.16 (#2401)
• c0ed56d Preserve system download policy when applying metadata (#2395)
• 3b8b5c5 Install Node hooks through git url (#2394)
• ff11cbb Implement requirements-txt-fixer as a builtin hook (#2390)
• c7dfc32 Match identify tags across filename parts (#2399)
• 928dc5c Speed up mixed-line-ending scans with memchr2 (#2391)
• 6c89849 Honor filenames in builtin hook entry and args (#2389)
• 28bc3f0 Add description for no-commit-to-branch (#2388)
• 1d9addd Reduce blocking-pool overhead in file hooks (#2384)
• Additional commits viewable in compare view

[rtibblesbot]

🔵 Review posted

Last updated: 2026-08-01 00:56 UTC

[rtibblesbot]

PR #232 — prek 0.4.5 → 0.4.11 (uv/PyPI), dev-only dependency ([dependency-groups].dev), lockfile-only diff (20/20 lines, all inside the prek package block; no transitive changes).

Semver: patch-level, but pre-1.0 so these releases carry features — treated as minor.

Breaking changes: none affecting this repo. The only rename in range is 0.4.8's auto-update → update; the two prek references here (pyproject.toml:41, .github/workflows/pre-commit.yml:32) don't invoke it.

Security fixes: none in the prek changelog for this range.

Peer dependencies: none — prek ships as a self-contained binary wheel.

Worth knowing:

• 0.4.9 changes the cached-hook-environment identity schema; existing envs are invalidated and reinstalled automatically. One slow local run after upgrading, no action needed.
• 0.4.11 fixes file matching (#2389, #2399). CI evidence below shows this repo's hooks match and pass unchanged.

CI: failing, but not from this bump. The workflow pins the action, not the tool — j178/prek-action@v2.0.4 already resolved and logged Using prek 0.4.11, so the run is the compatibility test: every hook passed under 0.4.11 except the repo's own local rebuild-from-specs, which rewrites js/package.json from 0.2.18 → 0.2.19 because setuptools-scm derives a dev version on any branch past tag v0.2.18. All four open PR branches fail identically, including two that don't touch uv.lock; main is green at the tagged commit. Not fixable in a dependabot lockfile PR — needs a fix on main (bump js/package.json, or make set_package_json_version non-mutating when the derived version has a .devN/local segment). Worth a tracking issue, since it blocks every PR. Note mergeStateStatus is BLOCKED, so merging still needs lint green or an admin override.

Approving on the dependency merits.

---

@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly

How was this generated?

Ran a dependency-update review pipeline over the version bump:

• Classified the bump by semver (patch / minor / major) and dependency type (production vs. development)
• Extracted the changelog and release notes across the version range
• Assessed compatibility with this project's usage and whether any code changes are required
• Treated CI as the primary safety net
• Scaled the review depth to the update's risk
• Chose the verdict from semver risk, changelog findings, and CI status

[rtibbles]

@dependabot rebase

[rtibbles]

No concerns, no issues from CI.