chore: update pre-commit hooks #575
Conversation
![pre-commit-ci[bot]](https://avatars.githubusercontent.com/in/68672?s=80&v=4){kind=small}
![scitools-ci[bot]](https://avatars.githubusercontent.com/in/212324?s=60&v=4){kind=small}
There was a problem hiding this comment.
Templating
Version numbers are not typically covered by templating. It is expected that this PR is 100% about advancing version numbers, which would not require any templating follow-up. Please double-check for any other changes that might be suitable for templating.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #575 +/- ##
=======================================
Coverage 95.62% 95.62%
=======================================
Files 39 39
Lines 4687 4687
=======================================
Hits 4482 4482
Misses 205 205 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
0ec856c to
f20e30d
Compare
There was a problem hiding this comment.
Templating
Version numbers are not typically covered by templating. It is expected that this PR is 100% about advancing version numbers, which would not require any templating follow-up. Please double-check for any other changes that might be suitable for templating.
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
f20e30d to
b68893f
Compare
There was a problem hiding this comment.
Templating
Version numbers are not typically covered by templating. It is expected that this PR is 100% about advancing version numbers, which would not require any templating follow-up. Please double-check for any other changes that might be suitable for templating.
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
b68893f to
499e6d1
Compare
There was a problem hiding this comment.
Templating
Version numbers are not typically covered by templating. It is expected that this PR is 100% about advancing version numbers, which would not require any templating follow-up. Please double-check for any other changes that might be suitable for templating.
updates: - [github.com/astral-sh/ruff-pre-commit: v0.12.11 → v0.13.3](astral-sh/ruff-pre-commit@v0.12.11...v0.13.3) - [github.com/adamchainz/blacken-docs: 1.19.1 → 1.20.0](adamchainz/blacken-docs@1.19.1...1.20.0) - [github.com/pre-commit/mirrors-mypy: v1.17.1 → v1.18.2](pre-commit/mirrors-mypy@v1.17.1...v1.18.2) - [github.com/scientific-python/cookie: 2025.05.02 → 2025.10.01](scientific-python/cookie@2025.05.02...2025.10.01)
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
499e6d1 to
ee2fefd
Compare
There was a problem hiding this comment.
Templating
Version numbers are not typically covered by templating. It is expected that this PR is 100% about advancing version numbers, which would not require any templating follow-up. Please double-check for any other changes that might be suitable for templating.
1 participant
updates:
@scitools-templating: please no share prompt