chore(deps-dev): bump pre-commit from 4.6.0 to 4.6.1 - #6070
chore(deps-dev): bump pre-commit from 4.6.0 to 4.6.1#6070dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [pre-commit](https://github.com/pre-commit/pre-commit) from 4.6.0 to 4.6.1. - [Release notes](https://github.com/pre-commit/pre-commit/releases) - [Changelog](https://github.com/pre-commit/pre-commit/blob/main/CHANGELOG.md) - [Commits](pre-commit/pre-commit@v4.6.0...v4.6.1) --- updated-dependencies: - dependency-name: pre-commit dependency-version: 4.6.1 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
🔵 Review postedLast updated: 2026-08-01 01:03 UTC |
rtibblesbot
left a comment
rtibblesbot
left a comment
There was a problem hiding this comment.
PR #6070 bumps pre-commit 4.6.0 → 4.6.1 — a patch bump of a development-only dependency (requirements-dev.in, pinned ==, with the matching line in the compiled requirements-dev.txt).
- Breaking changes: none
- Deprecations: none
- Security fixes: none
- Peer/transitive dependency changes: none — the lockfile diff is exactly one line
- Code changes required: none
Upstream 4.6.1 is fixes-only: language: node hooks installed via git (npm 12.x compat), JULIA_DEPOT_PATH for language: julia, an error on mistyped --repo in autoupdate, a faster pre-push commit-existence check, and no duplicated conflicted filenames in run --all-files. This repo has no node or julia hooks, so those two are inert here; the --all-files and pre-push fixes apply and are strict improvements.
CI passing (file linting, Python unit tests; other checks skipped by path filters, expected for a requirements-only diff).
Minor note for future pre-commit bumps: the All file linting job uses pre-commit/action@v3.0.1, which installs its own unpinned pre-commit rather than syncing requirements-dev.txt — so green CI validates the hook config, not the pinned version in this diff. Immaterial at patch level; no action needed here.
@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
1 participant
Bumps pre-commit from 4.6.0 to 4.6.1.
Release notes
Sourced from pre-commit's releases.
Changelog
Sourced from pre-commit's changelog.
Commits
242ce8av4.6.1766e550Merge pull request #3727 from pre-commit/dedupe1558d06Merge pull request #3726 from pre-commit/exists-faster8a1c47aavoid duplicate files in --all-files during conflict2e01c99faster check of rev existing locally as a commit3613bf2Merge pull request #3701 from pre-commit/autoupdate-repos1d811d9Return an error for invalid --repo374d354Merge pull request #3711 from damonbayer/dmb_JULIA_DEPOT_PATH1e7994fset JULIA_DEPOT_PATHb2b9119Merge pull request #3719 from pre-commit/npm-unknown-optionsDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)