From 1f7c82f0d7d6668d1934b63f747dde90cd21fd2c Mon Sep 17 00:00:00 2001
From: James Lamb <jlamb@nvidia.com>
Date: Thu, 12 Feb 2026 12:51:12 -0600
Subject: [PATCH 1/2] update 'Versions and Tags' page: no 'nvidia' channel,
 other small fixes

---
 resources/versions.md | 32 +++++++++++++++++++++++++++-----
 1 file changed, 27 insertions(+), 5 deletions(-)

diff --git a/resources/versions.md b/resources/versions.md
index 3a7dceb667c..2cac700de34 100644
--- a/resources/versions.md
+++ b/resources/versions.md
@@ -47,20 +47,42 @@ These commands require that the logged-in user (`anaconda login`) is in the owne
 
 When release procedures are not well-established or some other accident has resulted in packages that may cause problems, we need to remove packages.
 
-`anaconda remove <channel>/<package>/<version>`
+```shell
+anaconda remove'<channel>/<package>/<version>'
+```
 
 A real example of this would be removing an accidentally published package for rapids-logger, with a version that doesn't make sense:
 
-`anaconda remove rapidsai-nightly/rapids-logger/0.2.27`
+```shell
+anaconda remove 'rapidsai-nightly/rapids-logger/0.2.27'
+```
 
 ### Copy files from one channel to another
 
-The recommended install command at time of writing is `conda create -n rapids-25.10 -c rapidsai-nightly -c conda-forge -c nvidia rapids=25.10 python=3.13 'cuda-version>=12.0,<=12.9'`. If a release is uploaded to the rapidsai channel and not the rapidsai-nightly channel, our install command will not see the packages on the `rapidsai` channel. It's just not in the channel list. If both channels were added, we would have to be very careful about strict channel priority, which could easily pick up older or alpha releases.
+The recommended install command for nightlies at time of writing is
+
+```shell
+conda create -n rapids-26.02 -c rapidsai-nightly -c conda-forge rapids=26.02 python=3.13 'cuda-version>=13.0,<=13.1.1'
+```
+
+If a release is uploaded to the `rapidsai` channel and not the `rapidsai-nightly` channel, our install command will not see the packages on the `rapidsai` channel.
+
+It's just not in the channel list.
+
+If both channels were added, we would have to be very careful about strict channel priority, which could easily pick up older or alpha releases.
 
 One solution to this is to just copy the published packages to both `rapidsai` and `rapidsai-nightly`.
 
-`anaconda copy <source channel>/<package>/<version> --to-owner <destination channel>`
+```shell
+anaconda copy \
+    '<source channel>/<package>/<version>' \
+    --to-owner '<destination channel>'
+```
 
 and a real example:
 
-`anaconda copy rapidsai/rapids-logger/0.2.2 --to-owner rapidsai-nightly`
+```shell
+anaconda copy \
+    'rapidsai/rapids-logger/0.2.2' \
+    --to-owner 'rapidsai-nightly'
+```

From f4b6ab90498d2440ce83aa19c34dc62c7a8c8c9b Mon Sep 17 00:00:00 2001
From: James Lamb <jaylamb20@gmail.com>
Date: Tue, 24 Feb 2026 16:25:37 -0600
Subject: [PATCH 2/2] Apply suggestion from @jameslamb

---
 resources/versions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/resources/versions.md b/resources/versions.md
index 2cac700de34..57fa4bcb2cb 100644
--- a/resources/versions.md
+++ b/resources/versions.md
@@ -62,7 +62,7 @@ anaconda remove 'rapidsai-nightly/rapids-logger/0.2.27'
 The recommended install command for nightlies at time of writing is
 
 ```shell
-conda create -n rapids-26.02 -c rapidsai-nightly -c conda-forge rapids=26.02 python=3.13 'cuda-version>=13.0,<=13.1.1'
+conda create -n rapids-26.04 -c rapidsai-nightly -c conda-forge rapids=26.04 python=3.13 'cuda-version>=13.0,<=13.1.1'
 ```
 
 If a release is uploaded to the `rapidsai` channel and not the `rapidsai-nightly` channel, our install command will not see the packages on the `rapidsai` channel.