Use canary_channel instead of canary-channel

conda · Dec 2, 2024 · 04646da · 04646da
1 parent ca3f381
commit 04646da
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/templates/config.yml b/templates/config.yml
@@ -43,7 +43,7 @@ conda/infrastructure:
   # - src: templates/releases/RELEASE.md
   #   dst: RELEASE.md
   #   with:
-  #     canary-channel: https://anaconda.org/conda-canary
+  #     canary_channel: https://anaconda.org/conda-canary
   #     # CalVer placeholders
   #     placeholder: YY.M.PATCH
   #     placeholder_x: YY.M.x

diff --git a/templates/releases/RELEASE.md b/templates/releases/RELEASE.md
@@ -117,7 +117,7 @@ Let various interested parties know about the upcoming release; at minimum, cond
 
 ### Canary Builds for Manual Testing
 
-Once the release PRs are filed, successful canary builds will be available on `[[ canary-channel ]]/[[ repo.name ]]/files?channel=rc-[[ repo.name ]]-[[ placeholder_x ]]` for manual testing.
+Once the release PRs are filed, successful canary builds will be available on `[[ canary_channel ]]/[[ repo.name ]]/files?channel=rc-[[ repo.name ]]-[[ placeholder_x ]]` for manual testing.
 
 > [!NOTE]
 > You do not need to apply the `build::review` label for release PRs; every commit to the release branch builds and uploads canary builds to the respective `rc-` label.