chore(deps): bump sphinx-needs from 7.0.0 to 8.0.0

[dependabot]

Bumps sphinx-needs from 7.0.0 to 8.0.0.

Release notes

Sourced from sphinx-needs's releases.

8.0.0

See https://sphinx-needs.readthedocs.io/en/stable/changelog.html

What's Changed

• 📚 Fix 7.0.0 release date by @​ubmarco in useblocks/sphinx-needs#1666
• 🐛 Fix linkcheck CI job warnings by @​Copilot in useblocks/sphinx-needs#1667
• 🧪 Add tests for variants in links by @​ubmarco in useblocks/sphinx-needs#1669
• 📚 DOCS: add sphinx-ai-index to sphinx docs builder by @​Felix-Ruh in useblocks/sphinx-needs#1671
• ♻️ Introduce NeedLink structured internal representation for links by @​chrisjsewell in useblocks/sphinx-needs#1670
• 🔧 Use NeedLink directly in update_back_links function by @​chrisjsewell in useblocks/sphinx-needs#1672
• ♻️ Store NeedLink instead of str in LinksLiteralValue and LinksFunctionArray by @​chrisjsewell in useblocks/sphinx-needs#1673
• ♻️ Add _split_link_list parser with condition syntax support by @​chrisjsewell in useblocks/sphinx-needs#1674
• ✨ Add conditional need link assessment by @​Copilot in useblocks/sphinx-needs#1675
• 🔧 Use get_links(as_str=False) in needextend to avoid round-trip serialization by @​chrisjsewell in useblocks/sphinx-needs#1678
• 🔧 Store NeedPartData.backlinks as NeedLink instead of str by @​chrisjsewell in useblocks/sphinx-needs#1679
• 👌 Parse link conditions from imported and external needs by @​chrisjsewell in useblocks/sphinx-needs#1680
• 👌 Add needs_json_include_link_conditions config option by @​Copilot in useblocks/sphinx-needs#1681
• ♻️ Store NeedLink on NeedRef node at parse time instead of re-parsing later by @​Copilot in useblocks/sphinx-needs#1682
• 🔧 Bump ENV_DATA_VERSION to 4 for NeedLink storage format change by @​Copilot in useblocks/sphinx-needs#1683
• 👌 Add parse_conditions configuration for link types by @​Copilot in useblocks/sphinx-needs#1684
• ♻️ Fix links_from_content to use parsed doctree nodes instead of regex by @​chrisjsewell in useblocks/sphinx-needs#1685
• 🧪 Add some more tests for links_from_content by @​chrisjsewell in useblocks/sphinx-needs#1686
• 🚀 Release v8.0.0 by @​chrisjsewell in useblocks/sphinx-needs#1688

New Contributors

• @​Felix-Ruh made their first contribution in useblocks/sphinx-needs#1671

Full Changelog: useblocks/sphinx-needs@7.0.0...8.0.0

Changelog

Sourced from sphinx-needs's changelog.

8.0.0

:Released: Unreleased :Full Changelog: v7.0.0...v8.0.0 <https://github.com/useblocks/sphinx-needs/compare/7.0.0...5b223fd71eeb7402d5b60c1a5832434d8fd05e31>__

This release introduces conditional link assessment — the ability to attach :ref:filter_string conditions to links that are checked against the target need at build time. It also overhauls the internal link representation and fixes links_from_content to use the parsed doctree instead of fragile regex matching.

Conditional link assessment ...........................

A major motivation for requirements-management tooling is ensuring traceability — not just that two needs are linked, but that the link is valid in context. For example, a specification should only link to requirements that are in an "open" or "approved" state, or a test should only reference an implementation at a compatible version.

Sphinx-Needs now supports this via inline conditions on link references (see :ref:need_conditional_links). Append a :ref:filter_string in square brackets after the target ID:

.. code-block:: rst

.. spec:: My Specification :links: REQ_001[status=="open"], REQ_002[version>=3]

Each condition is evaluated against the target need's fields. If a condition evaluates to False, a needs.link_condition_failed warning is emitted; if the condition syntax is invalid, a needs.link_condition_invalid warning is emitted. Links without conditions continue to work exactly as before.

The condition is a standard :ref:filter_string expression, so you can use any Python-style comparison operators (==, !=, >, <, >=, <=), membership checks (in, not in), boolean connectives (and, or, not), and built-in helpers like search().

This means conditions already work with numeric fields such as integer or number (decimal) types. For example, if you define a version field:

.. code-block:: toml

[needs.fields.version] schema.type = "integer" nullable = false

You can then enforce version constraints on links:

... (truncated)

Commits

• 06e477a 🚀 Release v8.0.0 (#1688)
• 5b223fd 🧪 Add some more tests for links_from_content (#1686)
• 0411af3 ♻️ Fix links_from_content to use parsed doctree nodes instead of regex (#1685)
• d898e41 👌 Add parse_conditions configuration for link types (#1684)
• 36d4b70 🔧 Bump ENV_DATA_VERSION to 4 for NeedLink storage format change (#1683)
• bccacde ♻️ Store NeedLink on NeedRef node at parse time instead of re-parsing later (...
• 4473aef 👌 Add needs_json_include_link_conditions config option (#1681)
• e22e31d 👌 Parse link conditions from imported and external needs (#1680)
• 8ad874b 🔧 Store NeedPartData.backlinks as NeedLink instead of str (#1679)
• dce9f99 🔧 Use get_links(as_str=False) in needextend to avoid round-trip serializati...
• Additional commits viewable in compare view

[github-actions]

Test Results

191 tests  +191   191 ✅ +191   3m 47s ⏱️ + 3m 47s
  1 suites +  1     0 💤 ±  0 
  1 files   +  1     0 ❌ ±  0 

Results for commit b24b729. ± Comparison against base commit 2df3741.

♻️ This comment has been updated with latest results.