[chrisjsewell]

From #1970's held-back list. sphinx-needs capped jsonschema-rs at <0.54.0, and that cap was not a compatibility decision: dependabot's increase strategy wrote it in #1851, and it held the lock at 0.53.0 while 0.54.0 to 0.58.2 were released, all in September. This widens it to >=0.37.1,<0.59, keeping the floor and, since the project is pre-1.0, a next-minor cap. It relocks with uv lock --upgrade-package jsonschema-rs: 0.53.0 to 0.58.2, nothing else moves. The rest of the manifest hunk is taplo realigning the comment column, whitespace only.

API. The upstream Python changelog lists no breaking change to what sphinx-needs calls: validator_for, Validator, ValidationError, RegexOptions, and Draft7Validator in needsfile.py.

Entries that touch behaviour

• 0.55.0, Fixed: "absolute_keyword_location naming the sibling keyword whose validator carries the check …": no visible effect here, no snapshot changed.
• 0.57.0, Fixed: "The instance path of a schema build error, which was empty instead of naming the keyword location that failed to compile.": visible, see below.
• 0.58.2, Fixed: "schema_path of errors under a $ref or $dynamicRef to a named schema pointing at the resource root instead of that schema.": no visible effect here, no snapshot changed.

Snapshots. 11 of 240 schema snapshots changed, all in tests/schema/__snapshots__/test_schema.ambr and all the same one-line change, in the test_schema_config cases whose pattern does not compile under the safe regex options (look-arounds, back-references, atomic groups, conditionals, subroutine calls):

-  On instance:
+  On instance["properties"]["id"]["pattern"]:

["efforts"] and ["links"]["items"] appear in the extra-option and link cases. That is the 0.57.0 fix: compiling a schema with an invalid pattern through validator_for, the error's instance path is empty on 0.53.0 and 0.56.0 and names the keyword from 0.57.1 on (0.57.0 itself was replaced by 0.57.1 for a packaging issue). The Python-3.12-gated test_generate_schema snapshot is unchanged.

What users see. A needs_schema_definitions, needs_extra_options or needs_extra_links schema whose regex pattern is rejected now says where in the schema the pattern is, On instance["properties"]["id"]["pattern"]:, instead of a bare On instance:. Nothing else in sphinx-needs' output changes.

sphinx-needs 9.0.0 changelog draft line: - ⬆️ Allow jsonschema-rs up to 0.58: an invalid regex ``pattern`` in a schema now names its location in the error (``On instance["properties"]["id"]["pattern"]:``) rather than ``On instance:``.

Checked: poe lint, poe typecheck, the tooling tests, poe test-needs -n 4 (1805 passed), the Python 3.12 schema run (182 passed), and poe import-check-needs against jsonschema-rs 0.58.2 from PyPI.

#1970, the monthly lock update, also edits uv.lock; whichever lands second relocks.

[codecov]

Codecov Report

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

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1980   +/-   ##
=======================================
  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.