Skip to content

Update pre-commit hooks version to v6.0.0#896

Open
cclauss wants to merge 1 commit intoXRPLF:mainfrom
cclauss:patch-1
Open

Update pre-commit hooks version to v6.0.0#896
cclauss wants to merge 1 commit intoXRPLF:mainfrom
cclauss:patch-1

Conversation

@cclauss
Copy link

@cclauss cclauss commented Dec 21, 2025

https://github.com/pre-commit/pre-commit-hooks/releases

High Level Overview of Change

Context of Change

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Refactor (non-breaking change that only restructures code)
  • Tests (You added tests for code that already exists, or your new feature included in this PR)
  • Documentation Updates
  • Release

Did you update CHANGELOG.md?

  • Yes
  • No, this change does not impact library users

Test Plan

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 21, 2025

Walkthrough

Updates the pre-commit-hooks version from v2.3.0 to v6.0.0 in the repository's pre-commit configuration file. No other hooks, configuration settings, or control flow are modified.

Changes

Cohort / File(s) Change Summary
Pre-commit configuration
\.pre-commit-config\.yaml
Version bump: pre-commit-hooks updated from v2.3.0 to v6.0.0

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes


Poem

🐰 A version bump, so small and neat,
From two to six, the update's sweet,
Pre-commit hooks now fresh and bright,
The config file gleams in the light! ✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Description check ❓ Inconclusive The description is incomplete: the High Level Overview and Context sections are empty template comments, Type of Change is minimally filled (bug fix selected but without explanation), and Test Plan is not filled out. Fill in the High Level Overview with a summary of changes, provide context explaining why the upgrade was needed or chosen, and describe the test plan used to verify the changes.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'Update pre-commit hooks version to v6.0.0' clearly and specifically summarizes the main change in the pull request: updating the pre-commit-hooks dependency version.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1464e9e and f004dc6.

📒 Files selected for processing (1)
  • .pre-commit-config.yaml (1 hunks)

repos:
- repo: https://github.com/pre-commit/pre-commit-hooks
rev: v2.3.0
rev: v6.0.0
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify Python version requirements in the repository

echo "=== Checking Python version requirements in the repository ==="

# Check pyproject.toml for Python version
if [ -f "pyproject.toml" ]; then
  echo -e "\n--- pyproject.toml Python requirements ---"
  grep -i "python" pyproject.toml | head -20
fi

# Check setup.py for Python version
if [ -f "setup.py" ]; then
  echo -e "\n--- setup.py Python requirements ---"
  grep -i "python_requires\|version" setup.py | head -10
fi

# Check setup.cfg for Python version
if [ -f "setup.cfg" ]; then
  echo -e "\n--- setup.cfg Python requirements ---"
  grep -i "python_requires\|version" setup.cfg | head -10
fi

# Check for any .python-version files
echo -e "\n--- Checking for .python-version or similar ---"
fd -t f '\.python-version|\.tool-versions' 2>/dev/null | while read file; do
  echo "File: $file"
  cat "$file"
done

# Check CI configuration files for Python versions
echo -e "\n--- CI/CD Python versions ---"
fd -e yml -e yaml 2>/dev/null | head -20 | while read file; do
  if grep -q -i "python" "$file" 2>/dev/null; then
    echo "File: $file"
    grep -i "python" "$file" | head -5
  fi
done

# Check for any tox.ini
if [ -f "tox.ini" ]; then
  echo -e "\n--- tox.ini ---"
  grep -i "python\|envlist" tox.ini | head -10
fi

Repository: XRPLF/xrpl-py

Length of output: 723


Incompatible Python version: v6.0.0 requires Python >= 3.9, but the project declares support for Python >= 3.8.1.

The update to v6.0.0 requires Python >= 3.9, but the project's pyproject.toml declares requires-python = ">=3.8.1". This update will drop support for Python 3.8.x users. Either upgrade the minimum Python requirement to 3.9 in pyproject.toml and remove the conditional dependency handling for Python 3.8, or stay on an older version of pre-commit-hooks that supports Python 3.8.

🤖 Prompt for AI Agents
.pre-commit-config.yaml around line 4: the pinned pre-commit-hooks rev "v6.0.0"
requires Python >=3.9 which conflicts with pyproject.toml's requires-python =
">=3.8.1"; either (A) bump pyproject.toml requires-python to ">=3.9" and remove
any code/conditional handling intended to support 3.8, then keep rev v6.0.0, or
(B) roll back the rev to the latest pre-commit-hooks release that supports
Python 3.8 (e.g., a v5.x tag) and keep pyproject.toml unchanged; apply the
chosen change consistently across CI configs and update changelogs/requirements
accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant