Versions

River version: 0.22.0
Python version: 3.12.8
Operating system: macOS 15.2

Describe the bug

Pre-commit only runs its checks on changed files.
If a configuration was changed in a way that should impact the CI's output but no code file was changed, Pre-commit will not report any error.
(Surprisingly, the option --all-files does not help here).

The CI for the most recent commit reports no typing error, but running MyPy manually does.

In this case, here is what I suspect happened:
In commit e069b67, MyPy's version was bumped to 1.13.0 (see the diff here).
This new version of MyPy enabled new checks.
But because some Python files were not touched since, the CI never reported the new errors.

Steps/code to reproduce

1. Checkout the main branch (currently at commit 5531ae5)
2. Run pre-commit run -a
3. See there are no errors
4. Run mypy river
5. 5 errors are reported

Expected behaviour

Pre-commit should report the MyPy errors, and not pass the MyPy hook.
Alternatively: The CI should report all errors, whether they are in modified files or not.