Unexpected lint fail on unrelated code changes

[jsstevenson]

Identified by @nataled: changes to markdown are getting hung up by a linting failure

• Original PR here: Update StandardizationGuidelines.md #2831
• GH action result here: https://github.com/OBOFoundry/OBOFoundry.github.io/actions/runs/21178161218/job/60912684086?pr=2831

[deepakunni3]

This has to do with a change in behavior in black 26.1.0 (released on Jan 18, 2026).

It looks like running with black==25.12.0 should fix the immediate issue of failing checks.

Perhaps we can handle this in two stages:

1. Pin black==25.12.0 in tox.ini so that we have a predictable linting behavior
2. Investigate the root cause of what change between black 25.12.0 and 26.1.0 resulted in this strange behavior

What do you think @jsstevenson ?

[jsstevenson]

Yeah, these changes are pretty immaterial -- this is a great illustration of why it's good to pin formatters to specific version!

screenshot because it'll be a bit laborious to reformat as markdown

[deepakunni3]

For posterity:

• Black 25.12.0 still had issues.
• Stepping down to Black 24.8.0 fixed the errant behavior.