Bump docutils from 0.22.4 to 0.23

[dependabot]

Bumps docutils from 0.22.4 to 0.23.

Commits

• See full diff 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)

[github-actions]

diff-shades results comparing this PR (9c81d5e) to main (ce1897a):

--preview style: no changes

--stable style: no changes

---

What is this? | Workflow run | diff-shades documentation

[loadingerror]

PR Quality Report

Repository: psf/black
PR: #5166 — Bump docutils from 0.22.4 to 0.23
Generated: 2026-06-15 22:54:46 UTC
Risk: 🟢 low (28/100)
Range: ce1897a → 9c81d5e

Summary

• Dependency manifest or lock file changed.
• Changed files: 1.
• Total additions/deletions: +1/-1.
• Risk score: 28/100 (low).

Main deterministic findings

• 🟠 medium/test_coverage: Source files changed, but no test files were changed in this PR.

Highest-risk files

File	Status	+	-	Risk	Reasons
pyproject.toml	modified	1	1	8	dependency file

SLM reviewer context

Reviewer summary

The pull request has been reviewed by Dependabot, which has identified a dependency issue with docutils in the psf/black repository. The issue is related to the source_files field in the pyproject.toml file, which was modified in the pull request.

Main risks

The main risk is that the source_files field in the pyproject.toml file was modified, but no test files were changed in this PR. This can lead to issues with the test coverage of the project, as the test files will not be included in the coverage report.

What to check manually

To verify that the source_files field in the pyproject.toml file was modified, you can open the file in a text editor and search for the line containing source_files. If the line is modified, you can manually update it to reflect the changes made in the pull request.

Questions for the PR author

If you have any questions about the changes made in the pull request, feel free to ask. The reviewer will be happy to help you verify the changes and provide feedback on the test coverage.

Suggested review attention level

Given the high risk of modifying the source_files field in the pyproject.toml file, the reviewer will suggest that the pull request should be reviewed with caution. The reviewer will also recommend that the pull request be updated to reflect the changes made in the pull request.

Conclusion

The pull request has been reviewed by Dependabot, which has identified a dependency issue with docutils in the psf/black repository. The issue is related to the source_files field in the pyproject.toml file, which was modified in the pull request. To verify that the source_files field in the pyproject.toml file was modified, you can open the file in a text editor and search for the line containing source_files. If the line is modified, you can manually update it to reflect the changes made in the pull request. If you have any questions about the changes made in the pull request, feel free to ask. The reviewer will be happy to help you verify the changes and provide feedback on the test coverage.

Human approval checklist

• I checked the highest-risk files above.
• I verified that tests are adequate for the changed behavior.
• I reviewed dependency, infrastructure, and configuration changes if present.
• I found no exposed secrets, debug leftovers, or unsafe temporary code.

This comment is managed by PR Quality Analyzer and will be updated on new PR commits.