docs/tutorial: remove outdated pre-release warning

This updates a tutorial that used to require a pre-release version of CUE and removes its outdated prose mentioning this fact. This had been missed during some previous change that updated the tutorial to use the now-sufficient stable version. Preview-Path: /docs/tutorial/working-with-the-central-registry/ Signed-off-by: Jonathan Matthews <[email protected]> Change-Id: I21222ab776a3fda03c7c64a8b8f34b537a4c4b3c Dispatch-Trailer: {"type":"trybot","CL":1200076,"patchset":2,"ref":"refs/changes/76/1200076/2","targetBranch":"master"}
cue-lang · Aug 27, 2024 · e705ddd · e705ddd
1 parent b24925a
commit e705ddd
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 27 deletions.
diff --git a/content/docs/tutorial/working-with-the-central-registry/en.md b/content/docs/tutorial/working-with-the-central-registry/en.md
@@ -9,7 +9,7 @@ tags:
 toc_hide: true
 ---
 
-{{{with _script_ "en" "use prelrelease"}}}
+{{{with _script_ "en" "HIDDEN: set up registry access"}}}
 mkdir -p $HOME/.config/cue
 cat <<EOD > $HOME/.config/cue/logins.json
 {"registries":{"registry.cue.works":{"access_token":"${TEST_USER_AUTHN_CUE_USER_NEW}","token_type":"Bearer"}}}
@@ -27,13 +27,6 @@ Along the way you will:
 - Create a module that depends on an existing, well-known module
 - Use `cue mod tidy` to automatically add dependencies and their versions to the `module.cue` file
 
-Note that this guide depends on a pre-release version of CUE:
-
-{{{with script "en" "cue version"}}}
-#ellipsis 1
-cue version
-{{{end}}}
-
 ## Login to the Central Registry
 
 {{{with step}}}

diff --git a/content/docs/tutorial/working-with-the-central-registry/gen_cache.cue b/content/docs/tutorial/working-with-the-central-registry/gen_cache.cue
@@ -10,8 +10,8 @@ package site
 								"initial config.cue": "pwzZX7JFr/MmdRfI3FCA4zWvOu7r0E9BOVxhxcpLQ3E="
 							}
 							multi_step: {
-								hash:       "DFSJHV8QMN5VRI2N021RT3HGDUJV0L43BUTDN46CIQE1QN1953O0===="
-								scriptHash: "309JG38ICM25CV4OUDBDNSEHGI2PDVAS73RPFA0JKVHBTJHU8CH0===="
+								hash:       "J5QHA1KTH42B8BH79RKV1G5V0A3RP5V7114F7LAKCMFGLU133STG===="
+								scriptHash: "GJ54NFDKNIU9S4SES5TA4K59P6HGVANA0UVCIEM5TFOR2ORO15RG===="
 								steps: [{
 									doc:      ""
 									cmd:      "mkdir -p $HOME/.config/cue"
@@ -26,15 +26,6 @@ package site
 											"""
 									exitCode: 0
 									output:   ""
-								}, {
-									doc:      "#ellipsis 1"
-									cmd:      "cue version"
-									exitCode: 0
-									output: """
-											cue version v0.10.0
-											...
-
-											"""
 								}, {
 									doc:      ""
 									cmd:      "cue mod init glacial-tech.example/frostyapp@v0"

diff --git a/hugo/content/en/docs/tutorial/working-with-the-central-registry/index.md b/hugo/content/en/docs/tutorial/working-with-the-central-registry/index.md
@@ -20,14 +20,6 @@ Along the way you will:
 - Create a module that depends on an existing, well-known module
 - Use `cue mod tidy` to automatically add dependencies and their versions to the `module.cue` file
 
-Note that this guide depends on a pre-release version of CUE:
-
-```text { title="TERMINAL" type="terminal" codeToCopy="Y3VlIHZlcnNpb24=" }
-$ cue version
-cue version v0.10.0
-...
-```
-
 ## Login to the Central Registry
 
 {{< step stepNumber="1" >}}