Bump prek from 0.3.8 to 0.3.11

[dependabot]

Bumps prek from 0.3.8 to 0.3.11.

Release notes

Sourced from prek's releases.

0.3.11

Release Notes

Released on 2026-04-27.

Highlights

Hook entries now have an explicit shell option for shell snippets. Set shell: sh, bash, pwsh, powershell, or cmd when an entry should be evaluated by that shell; leaving it unset keeps prek's direct argv execution.

prek auto-update can now filter tag candidates before choosing an update. Both options take glob patterns: use --include-tag to only consider matching tag names, and --exclude-tag to skip matching tags such as moving tags or prereleases.

Enhancements

• Add auto-update --exclude-repo <repo> to skip repos (#1983)
• Add auto-update --exit-code to exit with non-zero on updates (#2002)
• Add auto-update --include-tag <pattern>/--exclude-tag <pattern> to filter tags (#1984)
• Adds an explicit shell hook option for entries that should run as shell source (#2004)
• Make --hook-dir optional for hook-impl (#1989)
• Skip shim warning when --script-version is missing (#1990)

Bug fixes

• Install Ruby executable in gem bin (#2017)
• Use dedicated Android npm package (#1982)
• Use stable repo keys without breaking cached clones (#1995)

Documentation

• Explain prek name (#1980)
• Clarify pass_filenames concurrency docs (#1999)
• Reorganize documentation references (#2005)
• Clarify hook author manifest env docs (#1991)
• docs: add Sentry to users list (#1981)

Contributors

• @​j178

Install prek 0.3.11

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://github.com/j178/prek/releases/download/v0.3.11/prek-installer.sh | sh

... (truncated)

Changelog

Sourced from prek's changelog.

0.3.11

Released on 2026-04-27.

Highlights

Hook entries now have an explicit shell option for shell snippets. Set shell: sh, bash, pwsh, powershell, or cmd when an entry should be evaluated by that shell; leaving it unset keeps prek's direct argv execution.

prek auto-update can now filter tag candidates before choosing an update. Both options take glob patterns: use --include-tag to only consider matching tag names, and --exclude-tag to skip matching tags such as moving tags or prereleases.

Enhancements

• Add auto-update --exclude-repo <repo> to skip repos (#1983)
• Add auto-update --exit-code to exit with non-zero on updates (#2002)
• Add auto-update --include-tag <pattern>/--exclude-tag <pattern> to filter tags (#1984)
• Adds an explicit shell hook option for entries that should run as shell source (#2004)
• Make --hook-dir optional for hook-impl (#1989)
• Skip shim warning when --script-version is missing (#1990)

Bug fixes

• Install Ruby executable in gem bin (#2017)
• Use dedicated Android npm package (#1982)
• Use stable repo keys without breaking cached clones (#1995)

Documentation

• Explain prek name (#1980)
• Clarify pass_filenames concurrency docs (#1999)
• Reorganize documentation references (#2005)
• Clarify hook author manifest env docs (#1991)
• docs: add Sentry to users list (#1981)

Contributors

• @​j178

0.3.10

Released on 2026-04-21.

Enhancements

• Disallow rev for non-remote repos in schema (#1964)
• Hide up-to-date output in non-verbose mode (#1942)

... (truncated)

Commits

• 8e731a9 Bump version to 0.3.11 (#2018)
• 24302f7 Install Ruby executable in gem bin (#2017)
• adf72c6 Update Rust crate rayon to v1.12.0 (#2015)
• 95b8874 Update Rust crate webpki-root-certs to v1.0.7 (#2014)
• 2692d83 Update Rust crate libc to v0.2.185 (#2013)
• 1477025 Update Rust crate tokio to v1.52.1 (#2016)
• efaf804 Update Rust crate clap_complete to v4.6.2 (#2012)
• 12033f7 Update Rust crate clap to v4.6.1 (#2011)
• 96ebb94 Update Rust crate assert_cmd to v2.2.1 (#2010)
• 55da2dc Update GitHub Actions (#2008)
• Additional commits viewable in compare view

[rtibblesbot]

Routine patch update; safe to merge.

CI: Python unit tests all passing. Linting check failed due to rebuild-from-specs modifying js/package.json (version 0.2.17 → 0.2.18) — pre-existing mismatch unrelated to this bump.

Dependency Update Review

Package: prek 0.3.8 → 0.3.10 (spans two patch releases, 0.3.9 + 0.3.10)
Semver risk: Patch
Dependency type: Dev (listed under [dependency-groups] dev in pyproject.toml; not a production runtime dependency)
CI status: Tests passing; lint failing for an unrelated pre-existing reason (see above)

Changelog Analysis

Sources consulted:

• PR body (includes release notes and changelog for 0.3.9 and 0.3.10)

Breaking changes: None found in either release.

Other notable changes:

• 0.3.10: Improve merge conflict marker detection, hide up-to-date output in non-verbose mode, preserve frozen comment spacing in auto-update, prefer stable Rust toolchains (bug fix)
• 0.3.9: prek auto-update stricter about pinned revisions; can detect impostor commits; --check flag can fail on frozen-ref mismatches

Compatibility Assessment

• Project uses prek only as a pre-commit hook runner (dev tooling); no prek API surface is called from application code
• No peer dependency changes
• No code changes required
• uv.lock also updates exclude-newer from a pinned timestamp to 0001-01-01T00:00:00Z with a backwards-compatibility comment; this is driven by exclude-newer-span = "P7D" in pyproject.toml and is expected lockfile behavior

Recommendation

APPROVE — patch bump of a dev-only tool, no breaking changes, all tests green.

---

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

How was this generated?

Reviewed the pull request diff checking for:

• Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
• Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
• Architecture: duplicated concerns, minimal interfaces, composition over inheritance
• Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
• Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
• Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
• Checked CI status and linked issue acceptance criteria
• For UI changes: inspected screenshots for layout, visual completeness, and consistency

[rtibbles]

@dependabot rebase