chore(deps): update pre-commit hook psf/black to v26.3.0#31
Conversation
Signed-off-by: red-hat-konflux <126015336+red-hat-konflux[bot]@users.noreply.github.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Summary by CodeRabbit
WalkthroughUpdated the Black code formatter version in the pre-commit configuration file from 26.1.0 to 26.3.0. No changes to hooks, arguments, or structure. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.pre-commit-config.yaml:
- Line 4: Update the Black hook revision in .pre-commit-config.yaml from the
non-existent "26.3.0" to the published "26.1.0": locate the line containing the
rev value for the Black hook (currently "26.3.0") and change it to "26.1.0" so
pre-commit can install the correct package version.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b29ea0c3-c722-4abf-8fd2-4ec5895d4d0b
📒 Files selected for processing (1)
.pre-commit-config.yaml
| repos: | ||
| - repo: https://github.com/psf/black | ||
| rev: 26.1.0 | ||
| rev: 26.3.0 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Description: Verify Black 26.3.0 exists and check for security issues
# Check PyPI for Black version availability
echo "Checking if Black 26.3.0 exists on PyPI..."
curl -s https://pypi.org/pypi/black/26.3.0/json | jq -r '.info.version // "Version not found"'
# Check for security advisories
echo -e "\nChecking for security advisories..."
gh api graphql -f query='
{
securityVulnerabilities(first: 10, ecosystem: PIP, package: "black") {
nodes {
advisory {
summary
severity
publishedAt
}
vulnerableVersionRange
firstPatchedVersion {
identifier
}
}
}
}'Repository: RedHatInsights/ccx-upgrades-data-eng
Length of output: 327
🌐 Web query:
Black 26.3.0 security vulnerabilities CVE
💡 Result:
- There is no
black(Python formatter) release26.3.0on PyPI. The latest available release shown on PyPI is 26.1.0 (uploaded Jan 18, 2026). [1] - Known CVE affecting Black: CVE-2024-21503 (ReDoS / improper validation), reported as affecting versions prior to 24.3.0 and fixed in 24.3.0—so 26.1.0 is not in the affected range. [2][4]
- The upstream
psf/blackGitHub repo currently shows no published GitHub Security Advisories. [3]
If you meant “Black 24.3.0” (not 26.3.0): that’s the version commonly referenced as the fix version for CVE-2024-21503. [2][4]
Sources: [1] PyPI black project page, [2] SentinelOne CVE-2024-21503 entry, [3] psf/black GitHub security page, [4] Safety/ResolvedSecurity CVE-2024-21503 package impact pages.
Use Black 26.1.0 instead of 26.3.0—the latter does not exist on PyPI.
Black 26.3.0 is not published on PyPI; the latest available version is 26.1.0 (released Jan 18, 2026). The pre-commit configuration will fail when attempting to install this non-existent version. Update the revision to 26.1.0, which has no known security vulnerabilities.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In @.pre-commit-config.yaml at line 4, Update the Black hook revision in
.pre-commit-config.yaml from the non-existent "26.3.0" to the published
"26.1.0": locate the line containing the rev value for the Black hook (currently
"26.3.0") and change it to "26.1.0" so pre-commit can install the correct
package version.
1 participant
This PR contains the following updates:
26.1.0->26.3.0Note: The
pre-commitmanager in Renovate is not supported by thepre-commitmaintainers or community. Please do not report any problems there, instead create a Discussion in the Renovate repository if you have any questions.Release Notes
psf/black (psf/black)
v26.3.0Compare Source
Stable style
# type: ignorecomments would be merged with othercomments on the same line, preventing AST equivalence failures (#4888)
Preview style
ifguards incaseblocks were incorrectly split when the pattern hada trailing comma (#4884)
string_processingcrashing on unassigned long string literals with trailingcommas (one-item tuples) (#4929)
Packaging
frozen environments (#4930)
Performance
uvloop.install()in favor ofuvloop.new_event_loop()(#4996)
maybe_install_uvloopfunction tomaybe_use_uvloopto simplify loopinstallation and creation of either a uvloop/winloop evenloop or default eventloop
(#4996)
Output
version, since AST safety checks cannot parse newer syntax. Also replace the
misleading "INTERNAL ERROR" message with an actionable error explaining the version
mismatch (#4983)
Blackd
windows when winloop is installed. (#4996)
Integrations
blackrequirements in the GitHub Action whenuse_pyprojectisenabled so that only version specifiers are accepted and direct references such as
black @​ https://...are rejected. Users should upgrade to the latest version of theaction as soon as possible. This update is received automatically when using
psf/black@stable, and is independent of the version of Black installed by theaction. (#5031)
Documentation
wrap_comprehension_in,simplify_power_operator_hugging, andwrap_long_dict_values_in_parensfeatures(#4987)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.