[brtkwr]

Context

Three open Dependabot alerts on filelock in uv.lock (1 high, 2 low), all fixed in filelock 4.2.1, which requires Python 3.11 or newer. filelock is dev tooling only here (pulled in by pre-commit/virtualenv in the test dependency group).

Changes

• New [tool.uv.dependency-groups] entry: test = { requires-python = ">=3.11" }, so uv resolves that group for 3.11+ only and the lock holds a single filelock 4.2.4
• The published package keeps requires-python = ">=3.10": these hooks are installed by pre-commit in consumer repos, and about 15 of them run pre-commit on Python 3.10 (airflow-integration and two-logger pin python3.10 as the default language version), so a 3.11 floor would break hook installation there
• Test workflow moved from Python 3.10 to 3.11 because uv sync --all-groups now needs 3.11. No release needed, consumers pin tags

Scope / Non-goals

• No runtime dependency changes and no change to the published metadata
• Developer uv sync (with the test group) now needs Python 3.11+; CI no longer exercises 3.10 itself

Validation

• uv lock --upgrade-package "filelock>=4.2.1": lock now holds a single filelock 4.2.4 entry, the only other changes are 3.10-only entries dropping out (backports, and older duplicate versions that existed just for the 3.10 fork)
• CI on this PR runs the test suite on the new Python floor

Ticket

• None, dependency security chore (commit-msg hook skipped)

🤖 Generated with Claude Code

https://claude.ai/code/session_01QUnP8iomGUAisq7SWJwEkA

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-28T09:10:06.447530Z	1a5b4fd	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

☂️ Code Coverage

current status: ✅

Overall Coverage

Statements	Covered	Coverage	Threshold	Status
256	247	96%	0%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: 1a5b4fd by action🐍

[github-actions]

🖌 Pre-commit success 🏆

Details

Downloading virtualenv (5.3MiB)
 Downloaded virtualenv
Installed 12 packages in 12ms
[INFO] Initializing environment for https://github.com/pre-commit/pre-commit-hooks.
[WARNING] repo `https://github.com/pre-commit/pre-commit-hooks` uses deprecated stage names (commit, push) which will be removed in a future version.  Hint: often `pre-commit autoupdate --repo https://github.com/pre-commit/pre-commit-hooks` will fix this.  if it does not -- consider reporting an issue to that repo.
[INFO] Initializing environment for https://github.com/astral-sh/ruff-pre-commit.
[INFO] Initializing environment for local.
[INFO] Initializing environment for https://github.com/astral-sh/uv-pre-commit.
[INFO] Installing environment for https://github.com/pre-commit/pre-commit-hooks.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/astral-sh/ruff-pre-commit.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
[INFO] Installing environment for https://github.com/astral-sh/uv-pre-commit.
[INFO] Once installed this environment will be reused.
[INFO] This may take a few minutes...
check python ast.....................................(no files to check)Skipped
check for added large files..............................................Passed
check json...........................................(no files to check)Skipped
check for merge conflicts................................................Passed
check toml...............................................................Passed
check yaml...............................................................Passed
detect private key.......................................................Passed
fix end of files.........................................................Passed
pretty format json...................................(no files to check)Skipped
fix requirements.txt.................................(no files to check)Skipped
trim trailing whitespace.................................................Passed
ruff.................................................(no files to check)Skipped
ruff-format..........................................(no files to check)Skipped
uv-lock..................................................................Passed

Exit code: 0

Author ✍️@brtkwr

[Puvendhan]

LGTM. filelock 4.2.4 in the test group, which now needs 3.11. The hooks still support 3.10.