X-ORG-596: Only publish numeric version of docs - #614
Merged
josephine-wolf-oberholtzer merged 1 commit intoAug 4, 2026
Merged
Conversation
josephine-wolf-oberholtzer
requested review from
msarahan
and removed request for
a team
August 4, 2026 18:07
josephine-wolf-oberholtzer
added
improvement
josephine-wolf-oberholtzer
force-pushed
the
josephine/x-org-596-only-publish-numeric-version
branch
from
August 4, 2026 18:08
5261a44 to
ed4ec45
Compare
josephine-wolf-oberholtzer
force-pushed
the
josephine/x-org-596-only-publish-numeric-version
branch
from
August 4, 2026 18:12
ed4ec45 to
a9a7560
Compare
gforsyth
approved these changes
Aug 4, 2026
gforsyth
left a comment
gforsyth
left a comment
Contributor
There was a problem hiding this comment.
Loving that negative diff
But yeah, I like this plan
josephine-wolf-oberholtzer
deleted the
josephine/x-org-596-only-publish-numeric-version
branch
August 4, 2026 18:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributes to #596
For the shared workflow, let's only push the XX.YY versions of the docs to docs.nvidia.com. Pushing the friendly tags ("stable", "legacy", "nightly") is tricky to get correct when performed from a per-repo, per-branch build, so we're going to punt on that technique for this release and let it cook more.
Instead we'll use the deploy workflow (rapidsai/docs#820) to guarantee the correct friendly tags ("stable", "legacy", "nightly") are pushed to docs.nvidia.com in a coordinated way on a daily / on-demand basis, just like for docs.rapidsai.org.
To simplify backwards-compatibility, and to leave the door open to coordinating friendly tags on a per-repo basis, I'm leaving the "version-map" input as-is. We're just going to stop using it for the time being.