Backport #8449: Enable docs version picker

[josephine-wolf-oberholtzer]

Backport of #8449, contributing to #8423 for the 26.08 release.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 97c3de2d-9b32-40aa-9cbe-b78832904775

📥 Commits

Reviewing files that changed from the base of the PR and between 265b9da and 6443f86.

📒 Files selected for processing (1)

• docs/source/conf.py

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation
  • Added a version switcher to the documentation site.
  • Configured the switcher to display available cuML documentation versions and identify the current version.

Walkthrough

Configured the Sphinx HTML theme version switcher with the cuML versions manifest URL and the current documentation version.

Changes

Documentation version switcher

Layer / File(s)	Summary
Sphinx switcher configuration docs/source/conf.py	The HTML theme now uses the cuML versions manifest and current-version match value.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• rapidsai/cuml#8449: Both update docs/source/conf.py to configure the Sphinx documentation version switcher.

Suggested reviewers: betatim, jcrist, csadorf

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the backport and the main change: enabling the documentation version picker.
Description check	✅ Passed	The description accurately relates the backport to the documentation version picker and the 26.08 release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[jcrist]

[betatim]

Process question: in #8449 you said "I'll backport this after the release", is it already after the release? Kinda? I guess we don't need this to ship in any wheels/conda packages so we can wait to be sure to be sure?

[josephine-wolf-oberholtzer]

@betatim I checked with @gforsyth yesterday. He basically said that the packages have been cut and uploaded to their respective destinations, so changes to the release branches won't alter those packages now.

[csadorf]

/merge

[josephine-wolf-oberholtzer]

/merge

[csadorf]

@betatim I checked with @gforsyth yesterday. He basically said that the packages have been cut and uploaded to their respective destinations, so changes to the release branches won't alter those packages now.

Does this mean we can make updates to published docs of stable releases by pushing to the releases branch if necessary?

[josephine-wolf-oberholtzer]

@csadorf I believe so but:

• Updates going to docs.rapidsai.com need to be built via https://github.com/rapidsai/docs. That repo builds the docs site daily, and you can also trigger the build manually.
• Updates to 26.08 on docs.nvidia.com don't currently go out automatically because the GH action mechanism for that isn't on the release/26.08 branch, just main. Short term, I'm uploading those docs to their (not our) S3 bucket. For main and release/26.10 branches (and beyond) changes will go out automatically.