[binutils-gdb] [pre-commit] Require pre-commit v4.5.1

[Tom de Vries]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=32b096b73e232c6e61cbbbf6a391bce909df369a

commit 32b096b73e232c6e61cbbbf6a391bce909df369a
Author: Tom de Vries <tdevries@suse.de>
Date:   Tue Feb 3 17:45:38 2026 +0100

    [pre-commit] Require pre-commit v4.5.1
    
    In December 2025, pre-commit v4.5.1 was released.  We currently require v3.2.0
    (released in March 2023), or later.
    
    It occurred to me that allowing such a large range of releases might lead to
    developers experiencing different behaviors, perhaps running into bugs that
    are already fixed in later releases.
    
    Fix this by requiring the latest release, v4.5.1.
    
    The drawback is that we now require a more recent python: v3.10.
    
    [ In more detail, pre-commit requires:
    - at v3.2.0, python 3.8
    - since v3.6.0, python 3.9
    - since v4.4.0, python 3.10. ]
    
    Tested on x86_64-linux, python 3.13.11 by doing "pre-commit run --all-files".
    
    Approved-By: Tom Tromey <tom@tromey.com>

Diff:
---
 .pre-commit-config.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
index 15270cda30c..9da588d4c4e 100644
--- a/.pre-commit-config.yaml
+++ b/.pre-commit-config.yaml
@@ -37,7 +37,7 @@
 # See https://pre-commit.com for more information
 # See https://pre-commit.com/hooks.html for more hooks
 
-minimum_pre_commit_version: 3.2.0
+minimum_pre_commit_version: 4.5.1
 default_install_hook_types: [pre-commit, commit-msg]
 default_stages: [pre-commit]
 repos: