Skip to content

[pre-commit.ci] pre-commit autoupdate - #200

Closed
pre-commit-ci[bot] wants to merge 2 commits into
mainfrom
pre-commit-ci-update-config
Closed

pre-commit-ci[bot] wants to merge 2 commits into
mainfrom
pre-commit-ci-update-config

Conversation

@pre-commit-ci

@pre-commit-ci pre-commit-ci Bot commented Aug 10, 2026 •

Copy link
Copy Markdown
Contributor

@pre-commit-ci
pre-commit-ci Bot requested a review from willyfh as a code owner August 10, 2026 17:25
updates:
- [github.com/pre-commit/mirrors-mypy: v2.3.0 → v2.3.1](pre-commit/mirrors-mypy@v2.3.0...v2.3.1)
- [github.com/pre-commit/mirrors-prettier: v3.1.0 → v4.0.0-alpha.8](pre-commit/mirrors-prettier@v3.1.0...v4.0.0-alpha.8)
- [github.com/astral-sh/ruff-pre-commit: v0.15.22 → v0.16.3](astral-sh/ruff-pre-commit@v0.15.22...v0.16.3)
@pre-commit-ci
pre-commit-ci Bot force-pushed the pre-commit-ci-update-config branch from ec49118 to 3d37e5a Compare August 17, 2026 17:32
@willyfh willyfh closed this Aug 23, 2026
willyfh added a commit that referenced this pull request Aug 23, 2026
…umps (#202)

pre-commit.ci's autoupdate always jumps to the highest available tag on the
mirrors-prettier repo, which only has v4 alpha pre-releases past v3.1.0 since
prettier hasn't cut a stable v4 yet. This has repeatedly produced broken
autoupdate PRs (#168, #188, #192, #200). Converting the hook to a local,
npm-pinned hook removes it from autoupdate's scope entirely.
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.

1 participant