Skip to content

chore(pip): bump the python group across 1 directory with 3 updates - #791

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/src/python-2148dcf177
Open

chore(pip): bump the python group across 1 directory with 3 updates#791
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pip/src/python-2148dcf177

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Bumps the python group with 3 updates in the /src directory: pydata-sphinx-theme, sphinx-mounts and sphinx-needs.

Updates pydata-sphinx-theme from 0.20.0 to 0.21.0

Release notes

Sourced from pydata-sphinx-theme's releases.

v0.21.0

What's Changed

Breaking

None.

Fixes

Improvements

Dependencies

New Contributors

Full Changelog: pydata/pydata-sphinx-theme@v0.20.0...v0.21.0

Commits
  • a52f5c9 Bump 0.20.0 -> 0.21.0 (#2472)
  • dc10572 Prevent "Back to Top" button from being cropped on firefox/android (#2442)
  • a9f2040 Bump astral-sh/setup-uv from 9.0.0 to 10.0.0 (#2468)
  • fe3f573 Bump py-cov-action/python-coverage-comment-action from 4.1 to 4.3 (#2467)
  • 3e15d01 fix: don't share sidebars between pages with non-flat output URIs (#2469)
  • c90610d fix: correct typo in source (#2459)
  • 051ac2c Avoid redundant processing when collapse_navigation=False (#2449)
  • ca91fce refactor: drop user-select rule superseded by Sphinx's basic.css (#2464)
  • 2a63b5c Bump js-yaml from 4.2.0 to 4.3.1 (#2463)
  • cbb254b Bump pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2 (#2460)
  • Additional commits viewable in compare view

Updates sphinx-mounts from 0.1.4 to 0.2.0

Release notes

Sourced from sphinx-mounts's releases.

0.2.0

What's Changed

New Contributors

Full Changelog: useblocks/sphinx-mounts@0.1.4...0.2.0

Changelog

Sourced from sphinx-mounts's changelog.

0.2.0

:Released: 2026-08-27

.. note::

Cache invalidation: the extension now declares an env_version, so the first build after upgrading discards its cached build environment and re-reads every document once. No action is required.

It is at 3 rather than 1 because both variant-gating keys — :ref:variant rules <variant-sources> and :ref:if on a mount entry <mount-gating> — change which docnames a project produces, and an environment written before those readers existed describes a document set this version would not have built. The second bump also covers a new field in the pickled shape of the mount-aware project.

  • sphinx-mounts now reads :ref:[[source.variant_sources]] <variant-sources>, the shared ubproject.toml key that decides which files are part of the build for the current build variant. Every rule whose if condition is false excludes its files; a file no false rule matches is unaffected. Rules only ever narrow, and their order does not matter.

    Host files leave through exclude_patterns, and files in a directory mount leave through that mount's own walk, so a rule reaches a bundle without knowing where it is mounted. A gating flip converges on the build where it happened, in both directions, without sphinx-build -E.

    No rule narrows a file-list mount — one declared with files = [...] rather than dir — under any rule spelling, and neither does ubCode's: a file-list mount's entries are an explicit request for named files and bypass pattern matching entirely. Use a directory mount for a bundle whose file set has to be narrowable by a rule.

    That is a statement about rules. A whole-mount if (below) gates a file-list mount exactly as it gates a directory one, in both tools. The two questions have opposite answers; per-file rule gating of a file-list mount stays unsupported.

    A project with no mounts at all can install sphinx-mounts purely for this, to have sphinx-build narrow its document set per variant exactly as ubCode_ does. Before this release the same ubproject.toml gave the two tools different document sets.

    The variant map is computed here rather than depended on: the JSON file named by variant_data_file is deep-merged under the inline [needs.variant_data] table, unconditionally. That is a no-op when Sphinx-Needs has already resolved, supplies the merge it has not performed yet on 8.3.1 and earlier, and is the whole computation when Sphinx-Needs is

... (truncated)

Commits
  • d23451a 🚀 Release v0.2.0 (#40)
  • 16d5854 ✨ Read if on a [[source.mounts]] entry: gate a whole bundle per variant (...
  • b0cc64e ✨ Read [[source.variant_sources]]: sphinx-build narrows its document set pe...
  • 72b5032 📚 Record ubCode's declared divergences in the mapping contract (#31)
  • 3467fee 🐛 Fix incremental attach_to staleness, collision detection and path-check rep...
  • See full diff in compare view

Updates sphinx-needs from 8.3.1 to 8.4.0

Release notes

Sourced from sphinx-needs's releases.

8.4.0

What's Changed

New Contributors

Full Changelog: useblocks/sphinx-needs@8.3.1...8.4.0

Changelog

Sourced from sphinx-needs's changelog.

8.4.0

:Released: 27.08.2026 :Full Changelog: v8.3.1...v8.4.0 <https://github.com/useblocks/sphinx-needs/compare/8.3.1...8.4.0>__

This release is about the view directives, and about a build that no longer stops at the first bad value. :ref:needflow gains a portable vocabulary — a :direction: that means the same thing on both engines, named legend configurations, and a :show_link_names: that says what each connection is labelled with — alongside a long list of fixes to both of its emitters. :ref:needs_card_layouts describes a need's card as a small dictionary instead of a hand-written layout string, :ref:list2need builds its needs directly and so works in Markdown documents and records the line each need was written on, and every view can cap what it shows with max_items. Running through the rest is one theme: configuration mistakes and render failures that used to end the build with a traceback are now located warnings, which leaves the rest of the build in place — and, for a project that builds with -W, can turn a green build red until the reported mistake is fixed or suppressed.

Improvements ............

  • ✨ :ref:list2need works in Markdown documents, and records the line each need was written on (:issue:1349, :pr:1790)

    The directive used to render every item into a need directive through a template and hand the result back to the parser. That step is gone: the items are built directly, and a nested item is placed inside its parent. The syntax and its parsing are untouched — the same list structure, the same (ID) capture, the same :delimiter: split, the same ((option="value")) region, the same validation — so a list that built before builds the same needs, with the same IDs, apart from the one class of item named under Breaking changes below.

    What the step cost, and is therefore fixed:

    • A list written as a {list2need} fence in a MyST Markdown document produced no needs at all, only an error naming a myst-parser internal. It now creates its needs, like any other directive.
    • Handing generated text back to the parser advanced its line counter for the rest of the file, so every need from the directive onwards — the items themselves, and any ordinary need directive written below them — was recorded at a line further down the file than it was written, by an amount that grew with each list in the document. Every lineno in needs.json is now the line the need was written on, inside an eval-rst block in a Markdown document too.
    • An item written () with options, such as * ()A title ((status="open")), lost them: they became body text. They are now set.

    Four inputs that used to be errors are now defined, none of which a document that built cleanly can contain:

... (truncated)

Commits
  • 4b0b3ab 🚀 Release v8.4.0 (#1792)
  • 82aa97b 📚 Number syntax-example rubrics in the ubCode preview (#1747)
  • 6885b7f 🐛 An invalid predicates expression warns instead of ending the build (#1791)
  • 6a6ffa5 ✨ list2need: build the needs directly, without generating reStructuredText (#...
  • eebe3b1 🐛 A need records the line it is actually written on (#1789)
  • 48269c0 🧪 Pin list2need behaviour and correct its documentation (#1788)
  • b42246a 👌 Resolve variant data while the configuration is initialised (#1787)
  • 88a32f6 ✨ needflow: portable direction, link-label and legend options (#1782)
  • c062feb 🧪 needflow: a shared conformance corpus for the portable vocabulary (#1781)
  • 53c7432 🐛 needflow: fix the graphviz label escaper, and stop bad configuration ending...
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Sep 1, 2026
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file python Pull requests that update python code labels Sep 1, 2026
@MaximilianSoerenPollak

MaximilianSoerenPollak commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@dependabot
chore(pip): bump the python group across 1 directory with 3 updates
d491989 
Bumps the python group with 3 updates in the /src directory: [pydata-sphinx-theme](https://github.com/pydata/pydata-sphinx-theme), [sphinx-mounts](https://github.com/useblocks/sphinx-mounts) and [sphinx-needs](https://github.com/useblocks/sphinx-needs).


Updates `pydata-sphinx-theme` from 0.20.0 to 0.21.0
- [Release notes](https://github.com/pydata/pydata-sphinx-theme/releases)
- [Changelog](https://github.com/pydata/pydata-sphinx-theme/blob/main/RELEASE.md)
- [Commits](pydata/pydata-sphinx-theme@v0.20.0...v0.21.0)

Updates `sphinx-mounts` from 0.1.4 to 0.2.0
- [Release notes](https://github.com/useblocks/sphinx-mounts/releases)
- [Changelog](https://github.com/useblocks/sphinx-mounts/blob/main/docs/source/changelog.rst)
- [Commits](useblocks/sphinx-mounts@0.1.4...0.2.0)

Updates `sphinx-needs` from 8.3.1 to 8.4.0
- [Release notes](https://github.com/useblocks/sphinx-needs/releases)
- [Changelog](https://github.com/useblocks/sphinx-needs/blob/master/docs/changelog.rst)
- [Commits](useblocks/sphinx-needs@8.3.1...8.4.0)

---
updated-dependencies:
- dependency-name: pydata-sphinx-theme
  dependency-version: 0.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: sphinx-mounts
  dependency-version: 0.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
- dependency-name: sphinx-needs
  dependency-version: 8.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: python
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot changed the title chore(pip): bump the python group in /src with 3 updates chore(pip): bump the python group across 1 directory with 3 updates Sep 2, 2026
@dependabot
dependabot Bot force-pushed the dependabot/pip/src/python-2148dcf177 branch from 6312880 to d491989 Compare September 2, 2026 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@AlexanderLanin AlexanderLanin Awaiting requested review from AlexanderLanin AlexanderLanin is a code owner
@MaximilianSoerenPollak MaximilianSoerenPollak Awaiting requested review from MaximilianSoerenPollak MaximilianSoerenPollak is a code owner
@dcalavrezo-qorix dcalavrezo-qorix Awaiting requested review from dcalavrezo-qorix dcalavrezo-qorix is a code owner
@nradakovic nradakovic Awaiting requested review from nradakovic nradakovic is a code owner
@a-zw a-zw Awaiting requested review from a-zw a-zw is a code owner

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file python Pull requests that update python code

Projects

INF - Infrastructure Community
Status: No status

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@MaximilianSoerenPollak