Skip to content

Conversation

@philderbeast
Copy link
Collaborator

@philderbeast philderbeast commented Jan 2, 2026

Fixes #11020. Bump the sphinx and rtd theme versions and remove the constraint on docutils that was in conflict. This allows building with Python-3.13.7, the version shipping with Ubuntu-25.10.

I heeded the warning fix, suggesting that html_theme_path not be set.

$ make users-guide --always-make
...
Running Sphinx v8.2.3
WARNING: Calling get_html_theme_path is deprecated. If you are calling it to
define html_theme_path, you are safe to remove that code.

  • Patches conform to the coding conventions.
  • Is this a PR that fixes CI? If so, it will need to be backported to older cabal release branches (ask maintainers for directions).

Copy link
Member

@Mikolaj Mikolaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you.

- Remove constraint on docutils
- Bump the python-version
- Bump os and python for rtd
@ulysses4ever
Copy link
Collaborator

Only needs a merge label now I think

@philderbeast philderbeast added the merge me Tell Mergify Bot to merge label Jan 7, 2026
@mergify mergify bot added ready and waiting Mergify is waiting out the cooldown period merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days queued labels Jan 7, 2026
@mergify
Copy link
Contributor

mergify bot commented Jan 9, 2026

Merge Queue Status

✅ The pull request has been merged at 07bcf69

This pull request spent 1 hour 45 minutes 36 seconds in the queue, including 1 hour 35 minutes 20 seconds running CI.
The checks were run on draft #11399.

Required conditions to merge
  • #approved-reviews-by >= 2 [🛡 GitHub branch protection]
  • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
  • any of [🛡 GitHub branch protection]:
    • check-success = Doctest Cabal
    • check-neutral = Doctest Cabal
    • check-skipped = Doctest Cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Meta checks
    • check-neutral = Meta checks
    • check-skipped = Meta checks
  • any of [🛡 GitHub branch protection]:
    • check-success = docs/readthedocs.org:cabal
    • check-neutral = docs/readthedocs.org:cabal
    • check-skipped = docs/readthedocs.org:cabal
  • any of [🛡 GitHub branch protection]:
    • check-success = Validate post job
    • check-neutral = Validate post job
    • check-skipped = Validate post job
  • any of [🛡 GitHub branch protection]:
    • check-success = fourmolu
    • check-neutral = fourmolu
    • check-skipped = fourmolu
  • any of [🛡 GitHub branch protection]:
    • check-success = hlint
    • check-neutral = hlint
    • check-skipped = hlint
  • any of [🛡 GitHub branch protection]:
    • check-success = Bootstrap post job
    • check-neutral = Bootstrap post job
    • check-skipped = Bootstrap post job
  • any of [🛡 GitHub branch protection]:
    • check-success = whitespace
    • check-neutral = whitespace
    • check-skipped = whitespace
  • any of [🛡 GitHub branch protection]:
    • check-success = Check sdist post job
    • check-neutral = Check sdist post job
    • check-skipped = Check sdist post job
  • any of [🛡 GitHub branch protection]:
    • check-success = Changelogs
    • check-neutral = Changelogs
    • check-skipped = Changelogs

mergify bot added a commit that referenced this pull request Jan 9, 2026
mergify bot added a commit that referenced this pull request Jan 9, 2026
@mergify mergify bot merged commit 3b433f5 into haskell:master Jan 9, 2026
242 of 244 checks passed
@mergify mergify bot removed the queued label Jan 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

merge delay passed Applied (usually by Mergify) when PR approved and received no updates for 2 days merge me Tell Mergify Bot to merge ready and waiting Mergify is waiting out the cooldown period

Projects

None yet

Development

Successfully merging this pull request may close these issues.

make users-guide fails with python >= 3.13

4 participants