⬆ Bump the python-packages group with 3 updates

[dependabot]

Bumps the python-packages group with 3 updates: prek, zizmor and alembic.

Updates prek from 0.4.11 to 0.4.12

Release notes

Sourced from prek's releases.

0.4.12

Release Notes

Released on 2026-08-03.

Enhancements

• Add --require-group for hook group intersections (#2472)
• Align fast-path and builtin pre-commit hooks (#2433)
• Do not shuffle file list for verbose output (#2431)
• Improve top-level command descriptions (#2429)
• Install uv from Astral CDN and drop source racing (#2455)
• Make prek install --force bypass external hooks paths (#2437)
• Show builtin hook flags in verbose list output (#2427)
• Verify uv release archive checksums (#2456)

Performance

• Precompute file tags in parallel (#2440)
• Skip diffs after known hook modifications (#2447)
• Skip worktree diffs for read-only languages (#2432)
• Track builtin hook file changes directly (#2404)

Bug fixes

• Use full object IDs in diff snapshots (#2448)

Documentation

• Add a multi-repository configuration example (#2434)
• Rewrite benchmark documentation (#2469)

Contributors

• @​j178
• @​BitWeaverDev
• @​allanlewis

Install prek 0.4.12

Install prebuilt binaries via shell script

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

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://github.com/j178/prek/releases/download/v0.4.12/prek-installer.ps1 | iex"
</tr></table> 

... (truncated)

Changelog

Sourced from prek's changelog.

0.4.12

Released on 2026-08-03.

Enhancements

• Add --require-group for hook group intersections (#2472)
• Align fast-path and builtin pre-commit hooks (#2433)
• Do not shuffle file list for verbose output (#2431)
• Improve top-level command descriptions (#2429)
• Install uv from Astral CDN and drop source racing (#2455)
• Make prek install --force bypass external hooks paths (#2437)
• Show builtin hook flags in verbose list output (#2427)
• Verify uv release archive checksums (#2456)

Performance

• Precompute file tags in parallel (#2440)
• Skip diffs after known hook modifications (#2447)
• Skip worktree diffs for read-only languages (#2432)
• Track builtin hook file changes directly (#2404)

Bug fixes

• Use full object IDs in diff snapshots (#2448)

Documentation

• Add a multi-repository configuration example (#2434)
• Rewrite benchmark documentation (#2469)

Contributors

• @​j178
• @​BitWeaverDev
• @​allanlewis

Commits

• 728238c Bump version to 0.4.12 (#2473)
• e5403ca Add --require-group for hook group intersections (#2472)
• 370fc41 Use ssl-certs to load custom certificates (#2470)
• 7cc64ca Rewrite benchmark documentation (#2469)
• 6a81c10 Update ubuntu Docker tag to v26 (#2466)
• 500a9d4 Run Conda tests sequentially (#2468)
• ebc1c38 Run .NET tests sequentially on Unix (#2467)
• 88fec17 Update Rust crate tokio-util to v0.7.19 (#2463)
• 9d9c9f5 Use full object IDs in diff snapshots (#2448)
• 0c7fc84 Update Rust crate tokio to v1.53.1 (#2462)
• Additional commits viewable in compare view

Updates zizmor from 1.28.0 to 1.29.0

Release notes

Sourced from zizmor's releases.

v1.29.0

New Features 🌈🔗

• zizmor now has experimental support for auditing pre-commit inputs, meaning both pre-commit configuration and hook definitions (#2209)

• New audit: insecure-url-scheme detects usages of insecure (i.e. plaintext) protocols when making network requests. The initial version of this audit is limited to pre-commit inputs only (#2228)

• zizmor now supports GitHub's "self-repository" reference syntax for local actions, e.g. uses: $/foo/bar instead of a manual checkout and uses: ./foo/bar (#2248)

Changes ⚠️🔗

• The unpinned-uses and unpinned-images audits have been separated more cleanly: unpinned-uses is now principally responsible for Git-style uses: clauses, whereas unpinned-images is now responsible for docker://-style uses: clauses (in addition to already checking other image references) (#2222)

Removals 🌅🔗

• --collect=workflows-only and --collect=actions-only have been fully removed. Use --collect=workflows and --collect=actions for the replacement behavior (#2242)

Bug Fixes 🐛🔗

• Fixed a bug where zizmor would reject a valid workflow definition for containing a literal jobs..outputs. value for being a non-string (#2220)

• Fixed a bug where the github-app audit would incorrectly flag some usages as needing a repositories: key, despite requesting organization-level-only permissions (#2227)

• Fixed a class of bugs where zizmor would discover the user's configuration in unintuitive ways. When auditing from a Git repository, zizmor now uses the repository root to discover configuration consistently (#2234)

Changelog

Sourced from zizmor's changelog.

1.29.0

New Features 🌈

• zizmor now has experimental support for auditing pre-commit inputs, meaning both pre-commit configuration and hook definitions (#2209)

• New audit: [insecure-url-scheme] detects usages of insecure (i.e. plaintext) protocols when making network requests. The initial version of this audit is limited to pre-commit inputs only (#2228)

• zizmor now supports GitHub's "self-repository" reference syntax for local actions, e.g. #!yaml uses: $/foo/bar instead of a manual checkout and #!yaml uses: ./foo/bar (#2248)

Changes ⚠️

• The [unpinned-uses] and [unpinned-images] audits have been separated more cleanly: [unpinned-uses] is now principally responsible for Git-style #!yaml uses: clauses, whereas [unpinned-images] is now responsible for docker://-style #!yaml uses: clauses (in addition to already checking other image references) (#2222)

Removals 🌅

• --collect=workflows-only and --collect=actions-only have been fully removed. Use --collect=workflows and --collect=actions for the replacement behavior (#2242)

Bug Fixes 🐛

• Fixed a bug where zizmor would reject a valid workflow definition for containing a literal jobs.<job>.outputs.<name> value for being a non-string (#2220)

• Fixed a bug where the [github-app] audit would incorrectly flag some usages as needing a #!yaml repositories: key, despite requesting organization-level-only permissions (#2227)

• Fixed a class of bugs where zizmor would discover the user's configuration in unintuitive ways. When auditing from a Git repository, zizmor now uses the repository root to discover configuration consistently (#2234)

Commits

• 3c11696 zizmor 1.29.0 (#2251)
• 876f448 Bump trophies (#2250)
• 3e92c0a Remove old deprecated --collect modes (#2242)
• 35ab77b Support self-repository syntax for local uses (#2249)
• 6ea55f5 chore(deps): bump pymdown-extensions from 10.21.3 to 11.0 (#2241)
• a56362c chore(deps): bump quinn-proto from 0.11.14 to 0.11.16 (#2240)
• 80b80f3 Bump zensical, fixup anchor IDs (#2239)
• dce1469 Bump trophies (#2238)
• fd487f4 chore(deps): bump the github-actions group with 4 updates (#2236)
• ab59a28 chore(deps): bump the cargo group with 11 updates (#2237)
• Additional commits viewable in compare view

Updates alembic from 1.18.5 to 1.19.0

Release notes

Sourced from alembic's releases.

1.19.0

Released: August 4, 2026

changed

• [changed] [installation] Environmental updates:

  -   Trove classifiers now include Python 3.15 which is now part of CI
      integration
  
  
  Python 3.14 is also added to trove classifiers which had been previously
  omitted
  
  
  Implemented PEP 604 style unions in type annotations
  

feature

• [feature] [autogenerate] Autogenerate now detects the addition and removal of named CHECK constraints, as part of the default autogenerate behavior. Detection is name-based only; a constraint whose name is unchanged is presumed equivalent regardless of its expression text, as reliably normalizing SQL expressions across backends for comparison purposes is not generally feasible. This behavior is implemented as a plugin named alembic.autogenerate.checkconstraint_byname, and may be disabled if not desired by excluding it from the EnvironmentContext.configure.autogenerate_plugins list. Pull request courtesy Francois van Kempen.

  References: #508

bug

• [bug] [commands] Fixed inconsistency where running stamp or downgrade to base in offline (--sql) mode would emit a DROP TABLE alembic_version statement, while the same operations in online mode never drop the version table. Offline mode no longer emits this DROP, matching online behavior. The version table continues to be created when it does not exist; only the spurious offline-only drop has been removed. Pull request courtesy imurodl.

  References: #1822

Commits

• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

This pull request has a merge conflict that needs to be resolved.

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.