From d8f8a7aad2223f5892e966bf22df832130afe26b Mon Sep 17 00:00:00 2001 From: SoluMilken Date: Mon, 16 Mar 2026 18:03:21 +0800 Subject: [PATCH] [Misc] Sync pre-commit to 4.5.1 in workflows and docs (#36675) Signed-off-by: SoluMilken Signed-off-by: Harry Mellor <19981378+hmellor@users.noreply.github.com> Co-authored-by: Harry Mellor <19981378+hmellor@users.noreply.github.com> --- .github/mergify.yml | 2 +- docs/contributing/README.md | 2 +- requirements/lint.txt | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/mergify.yml b/.github/mergify.yml index 0373c044890..c6d1f1fed52 100644 --- a/.github/mergify.yml +++ b/.github/mergify.yml @@ -27,7 +27,7 @@ pull_request_rules: Hi @{{author}}, the pre-commit checks have failed. Please run: ```bash - uv pip install pre-commit + uv pip install pre-commit>=4.5.1 pre-commit install pre-commit run --all-files ``` diff --git a/docs/contributing/README.md b/docs/contributing/README.md index 4e97ff69cec..24e7d1c5be0 100644 --- a/docs/contributing/README.md +++ b/docs/contributing/README.md @@ -75,7 +75,7 @@ For an optimized workflow when iterating on C++/CUDA kernels, see the [Increment vLLM uses `pre-commit` to lint and format the codebase. See if `pre-commit` is new to you. Setting up `pre-commit` is as easy as: ```bash -uv pip install pre-commit +uv pip install pre-commit>=4.5.1 pre-commit install ``` diff --git a/requirements/lint.txt b/requirements/lint.txt index 62446f94048..7d132113e0e 100644 --- a/requirements/lint.txt +++ b/requirements/lint.txt @@ -1,2 +1,2 @@ # formatting -pre-commit==4.0.1 +pre-commit>=4.5.1