[dependabot]

Bumps black from 26.5.1 to 26.10.1.

Release notes

Sourced from black's releases.

26.10.1

Highlights

This release fixes a security issue in Black's bundled GitHub Action. Repositories that use the action are encouraged to update to the latest version of Black immediately. This update is received automatically when using psf/black@stable, and is independent of the version of Black installed by the action.

When the GitHub Action reads version specifiers from tool.black.required-version, it now only accepts released versions of Black, as it already did for black requirements in dependency lists. Other values, such as URL references, are now rejected. This issue has been registered as GHSA-cg8m-r9f2-5wm2; a CVE identifier is pending.

Stable style

• Fix a long Jupyter notebook assignment magic (for example x = !ls -la) being wrapped in parentheses, which IPython can no longer run; such cells are now left unchanged (#5481)
• Keep repeated lines outside the selected --line-ranges unchanged (#5436)
• Fix --line-ranges formatting lines that follow a statement when formatting joins or re-indents that statement (#5484)
• Fix --line-ranges crashing with an internal error when an unselected statement has a # fmt: skip comment on the last line before a closing bracket (#5477)
• Prevent moving an encoding declaration (for example # -*- coding: latin-1 -*-) onto the first two lines of a file (#5487)
• Fix adding an extra trailing blank line inside a multi-line module docstring when its last line is near the line length limit (#5494)

Preview style

• Do not split short expressions on delimiters (such as binary operators, comparisons, or comprehensions) inside brackets when preceded by a standalone comment (#5455)
• Fix the unstable string_processing feature removing backslash-newline sequences from raw strings, which changed their value (#5482)
• Avoid adding unnecessary parentheses around unbreakable right-hand side expressions in assignments (such as annotated assignments or subscript targets) (#5473)
• Parenthesize expressions with parameter comments when they exceed the line length under --preview (#5442)
• Fix wrap_long_dict_values_in_parens dropping the parentheses around a right-hand side that contains a dictionary, leaving a line over the length limit (#5492)
• Fix the unstable string_processing feature adding a space after * or ** in a PEP 695 type parameter (* Ts = ...) when it splits a string in the parameter's default (#5504)
• Avoid unnecessary line splits of trailers (such as indexing/subscripts) when an earlier bracket split exceeds the line length only due to a trailing comment (#5498)

Configuration

• Add --cache-dir to configure the cache directory from the command line (#5433)
• Don't cache a file as formatted after formatting or checking it with --line-ranges,

... (truncated)

Changelog

Sourced from black's changelog.

Version 26.10.1

Highlights

This release fixes a security issue in Black's bundled GitHub Action. Repositories that use the action are encouraged to update to the latest version of Black immediately. This update is received automatically when using psf/black@stable, and is independent of the version of Black installed by the action.

When the GitHub Action reads version specifiers from tool.black.required-version, it now only accepts released versions of Black, as it already did for black requirements in dependency lists. Other values, such as URL references, are now rejected. This issue has been registered as GHSA-cg8m-r9f2-5wm2; a CVE identifier is pending.

Stable style

• Fix a long Jupyter notebook assignment magic (for example x = !ls -la) being wrapped in parentheses, which IPython can no longer run; such cells are now left unchanged (#5481)
• Keep repeated lines outside the selected --line-ranges unchanged (#5436)
• Fix --line-ranges formatting lines that follow a statement when formatting joins or re-indents that statement (#5484)
• Fix --line-ranges crashing with an internal error when an unselected statement has a # fmt: skip comment on the last line before a closing bracket (#5477)
• Prevent moving an encoding declaration (for example # -*- coding: latin-1 -*-) onto the first two lines of a file (#5487)
• Fix adding an extra trailing blank line inside a multi-line module docstring when its last line is near the line length limit (#5494)
• Keep the parentheses around a walrus that is the only item in a set (for example {(x := f())}) when targeting Python 3.9 or older, since Python 3.8 and 3.9.0 can't parse it without them (#5502)

Preview style

• Do not split short expressions on delimiters (such as binary operators, comparisons, or comprehensions) inside brackets when preceded by a standalone comment (#5455)
• Fix the unstable string_processing feature removing backslash-newline sequences from raw strings, which changed their value (#5482)
• Avoid adding unnecessary parentheses around unbreakable right-hand side expressions in assignments (such as annotated assignments or subscript targets) (#5473)
• Parenthesize expressions with parameter comments when they exceed the line length under --preview (#5442)
• Fix wrap_long_dict_values_in_parens dropping the parentheses around a right-hand side that contains a dictionary, leaving a line over the length limit (#5492)
• Fix the unstable string_processing feature adding a space after * or ** in a PEP 695 type parameter (* Ts = ...) when it splits a string in the parameter's default (#5504)
• Avoid unnecessary line splits of trailers (such as indexing/subscripts) when an earlier bracket split exceeds the line length only due to a trailing comment (#5498)

... (truncated)

Commits

• 258e7db Prepare release 26.10.1 (#5511)
• ac1f715 Action: validate required-version better (#5510)
• fe241cc Avoid splitting trailers when earlier bracket split exceeds length due to com...
• 4fb2897 Bump actions/upload-artifact from 7.0.1 to 7.0.2 (#5500)
• 6d0f557 Bump actions/download-artifact from 8.0.1 to 8.0.2 (#5501)
• c45f21d Handle PEP 695 type parameter whitespace in whitespace() (#5504)
• 8ec61a7 Skip UTF-8 BOM when reading .gitignore (#5497)
• c9b1148 Fix module docstring last_line_length when docstring ends with newline (#5494)
• eb88358 Parenthesize expressions with parameter comments in preview (#3113) (#5442)
• 939fa93 Keep the parentheses around a right-hand side when a dict value's parentheses...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

🤖 Claude Code Review

PR Review: Bump black from 26.5.1 to 26.10.1

The change is one line in pyproject.toml:73. It updates the lint dependency group pin for black on Python > 3.11. The pin for Python ≤ 3.11 stays at 25.11.0.

Code Quality

• ✅ Style conventions: The pin format matches the neighbouring entries.
• ✅ No commented-out code.
• ✅ Variable names: Not applicable.
• ✅ DRY: Not applicable. The split pins by Python version are the existing convention.
• ✅ Defects: I found none in the diff. Black is a dev-only lint dependency and doesn't affect runtime behavior. Two things to confirm in CI:
  • Black 26.x may change formatting rules, so the Black check could flag existing files. Look at the black --check result before merging.
  • The new version must still support every Python version in the matrix (3.12 and 3.13 here). I couldn't verify this offline.
• ✅ .claude/CLAUDE.md: It isn't modified by this PR. It is generic and has no local-environment-specific content.

Testing

• ✅ Unit and integration tests: None are needed for a dev-tooling version bump.
• ✅ Edge cases: Not applicable.
• ✅ Coverage: The PR doesn't change it.

Documentation

• ✅ README and API docs: No updates are needed.
• ✅ Inline comments: Not applicable.
• ⚠️ CHANGELOG.md: It isn't updated. Dependabot bumps of dev-only tooling usually don't need an entry, but check whether this repo's convention requires one.
• ✅ Markdown: No Markdown files changed.

Security

• ✅ No hardcoded credentials.
• ✅ Input validation and error handling: Not applicable.
• ✅ No sensitive data in logs.
• ✅ No license files: The diff has no .lic files and no strings starting with AQAAAD.

Summary

This is a low-risk, dev-only dependency bump and I have no blocking concerns. Before merging, confirm that the lint CI job passes on Python 3.12 and 3.13 with Black 26.10.1. Also decide whether the CHANGELOG needs an entry under this repo's conventions.

Automated code review analyzing defects and coding standards

[github-actions]

🤖 Claude Code Review

PR Review: Bump black 26.5.1 → 26.10.1

The change is one line in pyproject.toml:73. It bumps the lint extra's black pin for Python > 3.11. I reviewed only the diff and didn't run anything, so I haven't confirmed that the new version formats the existing code cleanly.

Code Quality

• ✅ Style: The pin format matches the neighbouring entries. It is exact (==) and keeps the same environment marker.
• ✅ No commented-out code
• ✅ Variable names: Not applicable.
• ✅ DRY: The split pin by Python version already exists, and this change keeps it.
• ✅ Defects: I found none. The <= 3.11 pin (black==25.11.0) is correctly left alone. Black 26.x needs Python 3.10 or later, and the project supports 3.10 to 3.13, which is why the marker is split. One thing to check in CI is whether black 26.10.1 reformats any files. If it does, the format check will fail until those files are reformatted.
• ✅ .claude/CLAUDE.md: It is untouched. It is generic and has no local-environment specifics.

Testing

• ✅ Unit and integration tests: Not applicable, because no code changed.
• ⚠️ Coverage: Not affected. CI must pass the lint and format check on Python 3.12 and 3.13 before merging.

Documentation

• ✅ README and API docs: No update needed.
• ✅ Inline comments: Not applicable.
• ✅ CHANGELOG: Dependabot bumps of dev-only tooling usually don't need an entry. Add one if this project's convention records dependency updates.
• ✅ Markdown: No Markdown files changed.

Security

• ✅ No hardcoded credentials
• ✅ Input validation and error handling: Not applicable.
• ✅ No sensitive data in logs
• ✅ No license files: The diff has no .lic files and no AQAAAD strings.

Summary

This is a low-risk, dev-only dependency bump with no blocking issues. It is safe to merge once CI is green, in particular the black format check on Python 3.12 and 3.13.

Automated code review analyzing defects and coding standards