Skip to content

chore(deps): update dependency pre-commit to v4.6.2 - #32

Open
FUMR-bot wants to merge 1 commit into
masterfrom
renovate/pre-commit-4.x-lockfile
Open

FUMR-bot wants to merge 1 commit into
masterfrom
renovate/pre-commit-4.x-lockfile

Conversation

@FUMR-bot

@FUMR-bot FUMR-bot commented Nov 17, 2025

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
pre-commit 4.3.04.6.2 age confidence

Release Notes

pre-commit/pre-commit (pre-commit)

v4.6.2

Compare Source

==================

Fixes

v4.6.1

Compare Source

==================

Fixes

v4.6.0

Compare Source

==================

Features
  • pre-commit hook-impl: allow --hook-dir to be missing to enable easier
    usage with git 2.54+ git hooks.
Fixes

v4.5.1

Compare Source

==================

Fixes
  • Fix language: python with repo: local without additional_dependencies.

v4.5.0

Compare Source

==================

Features

v4.4.0

Compare Source

==================

Features
Fixes

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@FUMR-bot

FUMR-bot commented Nov 17, 2025

Copy link
Copy Markdown
Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: poetry.lock
Creating virtualenv music-filesystem-WJpQueup-py3.14 in /home/ubuntu/.cache/pypoetry/virtualenvs
Updating dependencies
Resolving dependencies...

[SolverProblemError]
The current project's Python requirement (^3.9) is not compatible with some of the required packages Python requirement:
  - pytest requires Python >=3.10
  - pytest requires Python >=3.10
  - pytest requires Python >=3.10
  - pytest requires Python >=3.10
  - pytest requires Python >=3.10
  - pytest requires Python >=3.10

Because no versions of pytest match >9.0.0,<9.0.1 || >9.0.1,<9.0.2 || >9.0.2,<9.0.3 || >9.0.3,<9.1.0 || >9.1.0,<9.1.1 || >9.1.1,<10.0.0
 and pytest (9.0.0) requires Python >=3.10, pytest is forbidden.
And because pytest (9.0.1) requires Python >=3.10
 and pytest (9.0.2) requires Python >=3.10, pytest is forbidden.
And because pytest (9.0.3) requires Python >=3.10
 and pytest (9.1.0) requires Python >=3.10, pytest is forbidden.
So, because pytest (9.1.1) requires Python >=3.10
 and music-filesystem depends on pytest (^9.0.0), version solving failed.


@FUMR-bot FUMR-bot changed the title chore(deps): update dependency pre-commit to v4.4.0 chore(deps): update dependency pre-commit to v4.5.0 Nov 22, 2025
@FUMR-bot FUMR-bot changed the title chore(deps): update dependency pre-commit to v4.5.0 chore(deps): update dependency pre-commit to v4.5.1 Dec 16, 2025
@FUMR-bot FUMR-bot changed the title chore(deps): update dependency pre-commit to v4.5.1 chore(deps): update dependency pre-commit to v4.6.0 Apr 21, 2026
@FUMR-bot FUMR-bot changed the title chore(deps): update dependency pre-commit to v4.6.0 chore(deps): update dependency pre-commit to v4.6.1 Jul 21, 2026
@FUMR-bot FUMR-bot changed the title chore(deps): update dependency pre-commit to v4.6.1 chore(deps): update dependency pre-commit to v4.6.2 Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants