⬆️ Update the uv lock (monthly)

[useblocks-automation]

uv lock --upgrade, run by the monthly UV update workflow — every line uv's
lock diff reported, updates, additions and removals alike. Only uv.lock is
touched: the job asserts that no manifest changed, so every specifier here is still
the one someone chose by hand.

• contourpy: v1.3.3 -> v1.3.3, v1.4.0
• coverage: v7.16.0 -> v7.16.1
• docutils: v0.20.1, v0.21.2 -> v0.20.1, v0.22.4
• fonttools: v4.64.0 -> v4.65.0
• greenlet: v3.5.5 -> v3.5.6
• idna: v3.19 -> v3.20
• numpy: v2.4.6, v2.5.2 -> v2.4.6, v2.5.3
• platformdirs: v4.11.7 -> v4.11.9
• playwright: v1.62.0 -> v1.63.0
• pydata-sphinx-theme: v0.17.1, v0.19.0 -> v0.17.1
• syrupy: v6.0.0 -> v6.1.1
• ty: v0.0.80 -> v0.0.82
• urllib3: v2.7.0 -> v2.8.0
• uv: v0.12.13 -> v0.12.15

hooks clean after the upgrade: yes — see the workflow run

Held back by a manifest range

• jsonschema-rs: locked v0.53.0, newest v0.56.0, constraint "jsonschema-rs>=0.37.1,<0.54.0" (required by sphinx-needs)
• pydata-sphinx-theme: locked v0.17.1, newest v0.21.0, constraint "pydata-sphinx-theme>=0.15.2,<0.20.0" (required by sphinx-needs extra theme-pds)
• docutils: locked v0.22.4, newest v0.23, constraint "docutils" "docutils~=0.20.0" (required by sphinx-codelinks)
• tree-sitter: locked v0.25.2, newest v0.26.0, constraint "tree-sitter~=0.25.1" (required by sphinx-codelinks)
• sphinxcontrib-typer: locked v0.9.2, newest v0.10.0, constraint "sphinxcontrib-typer>=0.9.1" (required by sphinx-codelinks extra docs)

Direct dependencies only, from uv tree --outdated --depth 1 after the upgrade,
at the versions the DEFAULT resolution locks — a package held back only in a matrix
split (docutils 0.20.1 in typing, myst-parser 4.x in sphinx-7) is not listed.
The constraint column is every specifier this workspace writes for that name. What
actually blocks the newer release may be one of those, a cap elsewhere in the graph,
or a [tool.uv] conflicts split; uv lock --upgrade-package <name> names it.
Widening one is a pull request of its own, with the reason re-checked — never a
rider on this one.

Opened by the scheduled UV update workflow.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.70%. Comparing base (d68d10d) to head (1767dbc).
⚠️ Report is 11 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1970   +/-   ##
=======================================
  Coverage   91.69%   91.70%           
=======================================
  Files         129      129           
  Lines       18155    18152    -3     
=======================================
- Hits        16648    16647    -1     
+ Misses       1507     1505    -2     

Flag	Coverage Δ
codelinks	93.42% <ø> (ø)
mounts	94.03% <ø> (+0.01%)	⬆️
pytests	91.42% <ø> (+0.01%)	⬆️
reports	88.75% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[chrisjsewell]

The rehearsal dispatch of UV update (#1951's first run) opened this. Two of the 35 checks are red, and that is a finding rather than a fault in the job.

docutils: v0.20.1, v0.21.2 -> v0.20.1, v0.22.4 is an upgrade for the default resolution and a downgrade for the sphinx-7 and sphinx-8 cells: sphinx 7.4 and 8.2 cap docutils below 0.22, and uv lock --upgrade unified those splits on the 0.20.1 the typing group pins instead of keeping 0.21.2 — the version every cell had tested until now. At 0.20.1 one sphinx-mounts test fails, tests/test_warning_locations.py::test_showcase_integration_warning_location_is_absolute_mount_path[image]: the image.not_readable warning carries no line number.

That is docutils 0.20 behaviour, not sphinx-mounts. A plain Sphinx 8.2.3 project with no extensions prints index.rst:: for .. image:: missing.png at docutils 0.20.1 and index.rst:4: at 0.21.2 — 0.21 is where the image directive started stamping source and line on its node (docutils/parsers/rst/directives/images.py); before that the node inherits the parser's current position, which is unset for this shape. The same test passes at 0.21.2 in the same environment.

So this pull request waits on a floor decision: docutils>=0.21 across the workspace (which puts the two cells back on 0.21.2, with the typing group moving to the 0.21 series — measured as zero ty churn), or keep 0.20 and mark that one case expected-to-fail below 0.21. Once that lands, a re-dispatch of UV update rewrites branch uv-update and this pull request goes green. #1971 fixes the other thing the rehearsal showed: it arrived with no pkg: label (applied by hand here).