chore: update pre-commit hooks #571
Conversation
![pre-commit-ci[bot]](https://avatars.githubusercontent.com/in/68672?s=60&v=4){kind=small}
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
acda0be to
48ded74
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #571 +/- ##
=======================================
Coverage 58.40% 58.40%
=======================================
Files 62 62
Lines 6433 6433
Branches 1150 1150
=======================================
Hits 3757 3757
Misses 2385 2385
Partials 291 291 ☔ 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
48ded74 to
e34bef4
Compare
NOTE:re-spun checks, and the error on the main tests has now passed off. |
pre-commit-ci
bot
force-pushed
the
pre-commit-ci-update-config
branch
from
f6b5e25 to
c5ca3f6
Compare
![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.
updates: - [github.com/astral-sh/ruff-pre-commit: v0.9.10 → v0.11.2](astral-sh/ruff-pre-commit@v0.9.10...v0.11.2) - [github.com/abravalheri/validate-pyproject: v0.23 → v0.24.1](abravalheri/validate-pyproject@v0.23...v0.24.1)
pp-mo
force-pushed
the
pre-commit-ci-update-config
branch
from
c5ca3f6 to
a7e828c
Compare
ESadek-MO
dismissed
their stale review
Changes were just merging in PR, didn't affect actual template
updates: