ci: refresh dev dependencies

[github-actions]

No description provided.

[samccann]

@gotmax23 - we shouldn't be merging dependency changes w/o proof of testing. (I'm unfamiliar with what black does and if it hits the docs build or something else). Can you post how you tested this before merging?

Can you also clarify if this impacts something other than the docs builds?

[gotmax23]

The "refresh dev dependencies" and "refresh docs dependencies" PRs are two different things.

The dev dependencies do not affect the docs builds in any way. The only thing they affect are python linters (black, ruff, isort, mypy) that only touch two files¹: hacking/pr_labeler/label.py and noxfile.py. I have been acking and merging those once CI passes as we already discussed. There's nothing to test. The files either pass the linters or they require changes.

I have been leaving the docs build dependencies to you and @oraNod to review, test, and merge after there have been at least two approvals. Those are not being backported and are being handled as separate PRs.

Footnotes

1. I would like to apply these rules to the other Python code in this repository but have not yet. ↩