Repository navigation
chore: update filelock to 4.2.4 for its security fixes - #514
Conversation
filelock 4.2.1+ needs Python 3.11, so pre-commit (which pulls in filelock) is now only installed on Python 3.11 and newer. The action's own dependency group is unchanged.
Cpp-Linter Report
|
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Gate pre-commit by Python version pyproject.toml |
The pre-commit requirement now applies only when Python is 3.11 or later. |
Spelling configuration
| Layer / File(s) | Summary |
|---|---|
Add filelock to accepted words cspell.config.yml |
The spelling configuration now accepts filelock. |
Priority:
Estimated code review effort: 1 (Trivial) | ~3 minutes
Merge Risk: 
Minimal · up to c922a
-
The dependency update preserves Python 3.10 contributor and CI workflows while keeping filelock on supported Python versions.
Pre-merge checks: 
5
-
Full details: Docstring Coverage
-
Explanation
No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
Comment @coderabbitai help to get the list of available commands.
Fixes the open Dependabot alerts for
filelock(locked at 3.25.0). Dependabot can't open this update itself: the fixed releases (4.2.1+) need Python 3.11, while this project allows Python 3.10, so the resolver keeps picking 3.25.0.filelockonly comes in throughpre-commit(pre-commit → virtualenv → filelock), which is a dev dependency. The fix is the same as cpp-linter/clang-tools-pip#241:pre-commitin thedevgroup is now only installed on Python 3.11 and newer.uv lock --upgrade-package filelock: 3.25.0 → 4.2.4. (virtualenv is already at 21.14.13 from chore(deps): bump virtualenv from 21.14.9 to 21.14.13 in the security group across 1 directory #513.)No effect on the action itself. The action installs
--group action --no-dev, anduv export --group action --no-devgives the same list before and after this change (clang-tools 2.0.0, cpp-linter 1.15.1, git-bot-feedback 0.3.0, pyyaml 6.0.3). The lock was written with a current uv, so it stays atrevision = 5, and I checked that uv 0.9.5 (the version the action uses) accepts it withuv lock --checkand syncs the action group on Python 3.10 and 3.12.The only difference for contributors: on Python 3.10,
uv syncno longer installs pre-commit..python-versionis 3.12.Summary by CodeRabbit
pre-commitis now installed for development only with Python 3.11 or newer.