Skip to content

fix(deps): bump black >=24.0 → >=26.3.1 (CVE-2026-32274) #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
docdyhr merged 1 commit into from
Apr 1, 2026
Merged

fix(deps): bump black >=24.0 → >=26.3.1 (CVE-2026-32274) #129

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ dev = [
"pytest-timeout>=2.1",
"pytest-mock>=3.14",
"pytest-asyncio>=1.0",
"black>=24.0",
"black>=26.3.1",
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot Apr 1, 2026

Choose a reason for hiding this comment

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

P2 Badge Synchronize Black minimum across dependency manifests

Updating black to >=26.3.1 only in pyproject.toml leaves the alternate dev-install path on the old floor (requirements-dev.txt still has black>=23.7), and this path is actively documented/used (for example docs/CLAUDE_HOOKS_SETUP.md:103, docs/PYTHON313_SUPPORT.md:51, and scripts/update_dependencies.py:69). In environments that install with pip install -r requirements-dev.txt, the resolver can still pick vulnerable black<26.3.1, so this CVE remediation is incomplete unless the same minimum is applied to the requirements/constraints flow as well.

Useful? React with 👍 / 👎.

"ruff>=0.4",
"mypy>=1.10",
"types-PyYAML>=6.0.12",
Expand Down
Loading