py3-sphinx/9.1.0 package update

[octo-sts]

Commit: cc7c6f435ad37bb12264f8118c8461b230e6830c

Note: If you need to make manual changes to this PR, apply the skip:staging-update-bot label so the reconciler won't overwrite them.

[octo-sts]

🔢 Build Failed: Dependency Version Mismatch

ERROR: Package 'sphinx' requires a different Python: 3.11.14 not in '>=3.12'

Build Details

Category	Details
Build System	pip
Failure Point	python3.11 -m pip wheel command during py/pip-build-install step

Root Cause Analysis 🔍

The Sphinx package being built requires Python 3.12 or higher, but the build is attempting to use Python 3.11.14. This is a version compatibility issue where the package's minimum Python version requirement is not satisfied by the available Python interpreter.

---

🔍 Build failure fix suggestions

Found similar build failures that have been fixed in the past and analyzed them to suggest a fix:

Similar PRs with fixes

• py3-django/6.0 package update #73727

Suggested Changes

File: py3-sphinx.yaml

• modification at line 15-19 (data.py-versions.items section)
  Original:

data:
  - name: py-versions
    items:
      3.11: '311'
      3.12: '312'
      3.13: '313'

Replacement:

data:
  - name: py-versions
    items:
      3.12: '312'
      3.13: '313'

Content:

Remove Python 3.11 from the py-versions data items since Sphinx 9.1.0 no longer supports Python 3.11

• modification at line 98-102 (py3-supported-sphinx subpackage dependencies)
  Original:

  - name: py3-supported-${{vars.pypi-package}}
    description: meta package providing ${{vars.pypi-package}} for supported python versions.
    dependencies:
      runtime:
        - py3.10-${{vars.pypi-package}}
        - py3.11-${{vars.pypi-package}}
        - py3.12-${{vars.pypi-package}}
        - py3.13-${{vars.pypi-package}}

Replacement:

  - name: py3-supported-${{vars.pypi-package}}
    description: meta package providing ${{vars.pypi-package}} for supported python versions.
    dependencies:
      runtime:
        - py3.12-${{vars.pypi-package}}
        - py3.13-${{vars.pypi-package}}

Content:

Remove py3.10 and py3.11 dependencies from the meta package since these Python versions are no longer supported by Sphinx 9.1.0

Click to expand fix analysis

Analysis

The similar fix shows a clear pattern: when a package drops support for older Python versions, the build configuration must be updated to remove the unsupported Python versions from the py-versions data section and from all related subpackage dependencies. In the Django example, Python 3.10 and 3.11 were removed when Django 6.0 required Python 3.12+. The current Sphinx failure follows the same pattern - Sphinx 9.1.0 has dropped Python 3.11 support according to the changelog (#14153: Drop Python 3.11 support), but the build configuration still includes Python 3.11 in the py-versions data.

Click to expand fix explanation

Explanation

This fix addresses the root cause of the build failure by aligning the build configuration with Sphinx 9.1.0's actual Python version requirements. The error occurs because the build system is trying to build Sphinx for Python 3.11, but Sphinx 9.1.0 explicitly dropped Python 3.11 support (as noted in the changelog: '#14153: Drop Python 3.11 support'). By removing Python 3.11 from the py-versions data, the build system will no longer attempt to create a py3.11-sphinx package, eliminating the version compatibility error. The meta package dependencies are also updated to only include the actually supported Python versions (3.12 and 3.13), ensuring consistency across the package definition. This approach follows the exact same pattern used successfully in the Django fix, where unsupported Python versions were removed from both the py-versions data and the meta package dependencies.

Click to expand alternative approaches

Alternative Approaches

• Downgrade Sphinx to an older version that still supports Python 3.11, but this conflicts with Wolfi's principle of using the latest upstream versions
• Add Python 3.14 support if available upstream, though this would require additional testing and dependency verification
• Create a separate legacy package for Python 3.11 users, but this adds maintenance overhead and complexity

---

Was this comment helpful? Please use 👍 or 👎 reactions on this comment.