Pre-commit: Prevent use of pre-release revisions
New pre-commit script prevents the use of pre-release versions for hooks like isort.
A new script, gdb/contrib/pre-commit.py, has been introduced to enforce the use of stable, released versions for pre-commit hooks. This prevents accidental updates to pre-release versions of tools like isort, which previously led to broken configurations. The script checks revisions and errors out on pre-release tags, and isort has been reverted to its last stable release (8.0.1) to comply.
In Details
Introduces a custom pre-commit script (gdb/contrib/pre-commit.py) that checks for allowed revisions in .pre-commit-config.yaml. It specifically disallows pre-release tags (e.g., 9.0.0b1) for any repository, ensuring that only stable versions are used. This change reverts the isort revision back to 8.0.1 to satisfy this new check, addressing issues caused by isort's frequent pre-release tagging.
- pre-commit
- A framework for managing and automating pre-commit hooks. It allows developers to define a set of checks that run automatically before code is committed to version control, ensuring code quality and consistency.
- pre-release revision
- A version of software that is not yet officially released as stable. This includes alpha (a), beta (b), or release candidate (rc) versions, which are typically used for testing.
- isort
- A Python utility that automatically sorts imports in Python code. It helps to organize imports according to PEP 8 standards.