Publish versioned docs to docs.nvidia.com with a version switcher - #754
Conversation
…sh19/deployment into docs-nvidia-version-switcher
| - name: Set version | ||
| id: set-version | ||
| run: echo "VERSION=${{ startsWith(github.event.ref, 'refs/tags/') && 'stable' || 'nightly' }}" >> "$GITHUB_OUTPUT" | ||
| run: RAPIDS_DOCS_RELEASE_TAGS="$(git tag --list)" uv run make dirhtml SPHINXOPTS="-W --keep-going -n" |
There was a problem hiding this comment.
Just checking did we end up pushing to the rapids S3? are we ready to stop publishing the rapids docs?
There was a problem hiding this comment.
As soon as we get something on docs.nvidia.com we can stop publishing to docs.rapids.ai and add redirects.
bdice
left a comment
There was a problem hiding this comment.
Approving with very light review since this has to be merged to be tested.
|
Answering @ncclementi's question, we will now not have a switcher on local/ReadTheDocs builds. We previously had a switcher which was defined in a HTML file (see the older approach in PR changes), but the new NVIDIA theme has the option to enable the switcher only when a |
ncclementi
left a comment
There was a problem hiding this comment.
Let's merge this and see what happens, as we'll need to iterate

Addition to #722
This PR is intended to move publishing docs away from
stable/nightlyversioning and onto thelatest/YY.MMversioning scheme.datascience/deployment/latestdatascience/deployment/YY.MM(alpha tags do not publish)version.jsonis published next to those directories which enables the navbar version switcher.Both uploads go through the
publish-docsandpublish-one-docshared actions. The workflow itself has no logic in it, the Sphinx build writes a small ephemeral manifest atbuild/publish/publish.envwhich specifies where the files have to be published to which is picked up by the workflow.The
version.jsonis created from a new Sphinx extension calledrapids_docs_publishing. It runs only when the workflow setsRAPIDS_DOCS_PUBLISH=true, so local and ReadTheDocs builds do have show any switcher on the builds.This PR also stops publishing to the old
rapidsai-docsbucket and we will setup redirects onrapidsai/docsto redirect all links fromdocs.rapids.ai/deployment/*todocs.nvidia.com/datascience/deployment/*Can only be merged after rapidsai/shared-actions#142 is merged. [EDIT: This has been merged]