chore(deps): update dependency black to <25.9.1,>=25.9.0 #506
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/black-25.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
<25.2.0,>=25.1.0
-><25.9.1,>=25.9.0
Release Notes
psf/black (black)
v25.9.0
Compare Source
Highlights
await/async
as soft keywords/variable names(#4676)
Stable style
del
statement containing tuples (#4628)with
statements (#4630)
# fmt: skip
followed by a comment at the end of file (#4635)as
clause of awith
statement (#4634)with
statement (#4646)\
followed by a\r
followed by a comment (#4663)\\r\n
(#4673)await ...
(where...
is a literalEllipsis
) (#4676)(#4670)
Preview style
# fmt: skip
would stillbe formatted (#4552)
multiline_string_handling
with ternaries and dictionaries (#4657)string_processing
would not split f-strings directly afterexpressions (#4680)
in
clause of comprehensions across lines if necessary (#4699)except
andexcept*
withoutas
. (#4720)\r
style newlines to the potential newlines to normalize file newlines both fromand to (#4710)
Parser
parameter bounds and defaults. (#4602)
Performance
Integrations
psf/black
to read Black version from an additional section inpyproject.toml:
[project.dependency-groups]
(#4606)Documentation
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 is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Decision: Accept
Change Score: 10/10
This diff updates the version of
black
and its corresponding lock file. The changes appear to be correctly implemented, ensuring the project uses the specifiedblack
version. All necessary updates within the lock file (hashes, URLs, dependencies) are present, which is essential for dependency management and reproducibility. No problems were found.