Forward-merge release/26.04 into main

[jameslamb]

Replaces #7923

Fixes forward-merger conflicts.

[coderabbitai]

📝 Walkthrough

Walkthrough

The Sphinx documentation configuration was updated to remove the scipy intersphinx mapping entry from docs/source/conf.py, replacing the active mapping with TODO comments while preserving all other documentation linking configurations.

Changes

Cohort / File(s)	Summary
Documentation Configuration docs/source/conf.py	Removed active "scipy" entry from intersphinx_mapping and replaced it with commented-out TODO lines; all other intersphinx mappings remain unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Disable SciPy intersphinx #7935: Applies the same scipy intersphinx_mapping removal change to cuML's documentation configuration.

Suggested reviewers

• dantegd

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The pull request title accurately describes the main objective: forward-merging release/26.04 into main, which matches the changeset purpose.
Linked Issues check	✅ Passed	The PR successfully addresses issue #7923 by forward-merging release/26.04 into main and resolving merge conflicts, meeting the stated objective.
Out of Scope Changes check	✅ Passed	The change to disable SciPy intersphinx mappings in docs/source/conf.py is a legitimate conflict resolution from the release branch merge, not out-of-scope.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description check	✅ Passed	The pull request description directly addresses the changeset by explaining it resolves forward-merger conflicts and replaces a previous PR.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[jameslamb]

/merge nosquash

[rapids-bot]

Commit history integrity check failed: not all commits from original PR #7923 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

[rapids-bot]

Commit history integrity check failed: not all commits from original PR #7923 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

[rapids-bot]

Commit history integrity check failed: not all commits from original PR #7923 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

[rapids-bot]

Commit history integrity check failed: not all commits from original PR #7923 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

[rapids-bot]

Commit history integrity check failed: not all commits from original PR #7923 appear to be present individually in this PR's history. This usually happens if commits were squashed during the manual resolution process. Please ensure all original commits are preserved individually. You can fix this and try the /merge nosquash command again.

[jameslamb]

Yeah yeah ok ok. I'll do it manually.