Scheduled weekly dependency update for week 06 #650
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,7 +1,7 @@ | ||
| sphinx==9.1.0 | ||
| furo==2025.12.19 | ||
| sphinx-autobuild==2025.8.25 | ||
| sphinx-copybutton==0.5.2 | ||
| sphinx-sitemap==2.9.0 | ||
| sphinx-click==6.2.0 | ||
| sphinx-autodoc-typehints==3.6.2 | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,9 @@ | ||
| setuptools==82.0.0 | ||
| pytest==9.0.2 | ||
|
Comment on lines
+1
to
+2
There was a problem hiding this comment. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Check for pkg_resources usage in Python files
echo "=== Checking for pkg_resources usage ==="
rg 'from pkg_resources import|import pkg_resources' --type py --no-heading
# Check Python version requirements
echo -e "\n=== Checking Python version requirements ==="
for file in setup.py setup.cfg pyproject.toml; do
if [ -f "$file" ]; then
echo "--- $file ---"
cat "$file"
echo ""
fi
done
# Check for pytest configuration
echo -e "\n=== Checking pytest/tox configuration ==="
for file in pytest.ini tox.ini .pytest.ini; do
if [ -f "$file" ]; then
echo "--- $file ---"
cat "$file"
echo ""
fi
done
# Check pyproject.toml for tool.pytest section
if [ -f "pyproject.toml" ]; then
echo "--- pyproject.toml [tool.pytest] section ---"
rg '\[tool\.pytest' pyproject.toml -A 10
fiRepository: DagsHub/client Length of output: 2621 🌐 Web query:
💡 Result: In setuptools 82.0.0 (released 2026-02-08), What to do:
Sources: setuptools 82.0.0 changelog/history (removal notice) [1], setuptools 🌐 Web query:
💡 Result: pytest 9.0.2 breaking changes
Python version compatibility (pytest 9.0.2)
Sources: [1] pytest 9.0.2 release announcement, [2] pytest changelog (9.0.2 / 9.0.0 entries), [3] pytest Backwards Compatibility Policy (Python version support table. Address Python 3.9 compatibility issue with pytest 9.0.2. setuptools 82.0.0 removes
|
||
| respx==0.22.0 | ||
| pytest-git==1.8.0 | ||
| pytest-env==1.2.0 | ||
| pytest-mock==3.15.1 | ||
| fiftyone==1.12.0 | ||
| datasets==4.5.0 | ||
| ultralytics==8.4.13 | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🌐 Web query:
Sphinx 9.1.0 Python version requirements PyPI💡 Result:
Sphinx 9.1.0 on PyPI specifies Requires-Python: >= 3.12. [1]
Sources:
[1] PyPI – Sphinx 9.1.0 project page (Requires: Python >=3.12) (pypi.org)
Citations:
🌐 Web query:
Sphinx 9.0 breaking changes migration guide💡 Result:
Sphinx 9.0 (released Nov 30, 2025) — breaking/incompatible changes + migration checklist
Extension API:
create_source_parser()signature changedIf you call
SphinxComponentRegistry.create_source_parser()directly, update your call sites: it no longer acceptsappand instead takesconfigandenv. Audit any custom builders/parsers/extensions that touch this registry API. [1]Source file decoding is stricter (encoding issues can now hard-fail)
Non-decodable bytes in source files now raise an error (older Sphinx replaced them with
?and warned). Fix by ensuring your source files are valid text (and effectively UTF-8 going forward). [1]sphinx.ext.autodocwas substantially rewritten (edge-case incompatibilities)Most projects won’t notice changes, but extensions that interact with autodoc internals may break.
Mitigation: set
autodoc_use_legacy_class_based = Trueinconf.pyto temporarily use the pre-9.0 implementation while you adjust. [1]Search index content change (may affect search behavior/tests)
Sphinx no longer includes escaped title content in the search index. If you snapshot-test search output or rely on specific search indexing behavior, re-baseline those expectations. [1]
Deprecations introduced in 9.0 (fix now to avoid future major breaks)
.appattributes are deprecated (e.g.builder.app,env.app,events.app,SphinxTransform.app). Prefer using the objects’ supported APIs without reaching for.app. [1]Parser.set_application()is deprecated;Parser.configandParser.envattributes are deprecated. If you maintain a custom parser, update it to the new expectations (and avoid storing/reading config/env via those deprecated attributes). [1]sphinx.iois deprecated and will be removed in Sphinx 10—stop importing/depending on it. [1]Primary reference: Sphinx 9.0 changelog / incompatible changes & deprecations. [1]
Release index (to navigate 9.0.x point releases): changelog index. [2]
Sources
[1] Sphinx 9.0 changelog (incompatible changes, deprecations): (sphinx-doc.org)
[2] Sphinx changelog index (release navigation): (sphinx-doc.org)
Citations:
🏁 Script executed:
Repository: DagsHub/client
Length of output: 305
🌐 Web query:
Sphinx version 8 release skipped why💡 Result:
Sphinx didn’t skip version 8 (for the Python documentation generator). It was released as:
If you’re “not seeing” Sphinx 8, it’s usually because something in your toolchain restricted Sphinx to
<8(common right after release). For example,sphinx-rtd-themeinitially required Sphinx < 8, and users had to wait for that ecosystem support to be updated. [3]Sources:
[1] (sphinx-doc.org)
[2] (sphinx-doc.org)
[3] (github.com)
Citations:
Verify Sphinx 9.1.0 compatibility with breaking changes and confirm codebase uses no affected features.
Sphinx has a major version bump from 7.3.7 to 9.1.0. The Python version requirement increases from >=3.9 to >=3.12, meaning Python 3.9, 3.10, and 3.11 are no longer supported (not just 3.11 as suggested).
More significantly, Sphinx 9.0 introduced breaking changes that require verification:
create_source_parser()signature changed (no longer acceptsapp)sphinx.ext.autodocrewrite with potential incompatibilities (useautodoc_use_legacy_class_based = Trueas fallback)Confirm that the DagsHub client documentation setup does not use custom Sphinx extensions, parsers, or rely on autodoc features that would be affected by these changes. Verify
sphinx-autobuild==2025.8.25(requires Python >=3.11) is compatible with the Sphinx upgrade path.