chore: remove un-required version number and tidy docs (#685)

Azure · Nov 16, 2023 · ef8a90c · ef8a90c
1 parent 328a18b
commit ef8a90c
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/accelerator/.config/ALZ-Powershell.config.json b/accelerator/.config/ALZ-Powershell.config.json
@@ -512,7 +512,7 @@
         },
         "UpstreamReleaseVersion": {
             "Type": "Computed",
-            "Value": "v0.16.6",
+            "Value": "{REPLACED_BY_ALZ_POWERSHELL_MODULE}",
             "Targets": [
                 {
                     "Name": "UPSTREAM_RELEASE_VERSION",

diff --git a/docs/wiki/Accelerator.md b/docs/wiki/Accelerator.md
@@ -219,7 +219,7 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
 
 1. Using the ALZ PowerShell Module, there is a cmdlet called `Get-ALZBicepRelease`. This will download a specified release version from the remote ALZ-Bicep repository and pull down to the local directory where your Accelerator framework was initially deployed.
 
-    Here is an example of using the cmdlet to pull down version v0.16.5:
+    Here is an example of using the cmdlet to pull down version v0.16.6:
 
     ```powershell
     Get-ALZGithubRelease -githubRepoUrl "https://github.com/Azure/ALZ-Bicep" -release "v0.16.6" -directoryForReleases "C:\Repos\ALZ\accelerator\upstream-releases\"
@@ -228,7 +228,7 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
 1. Once the ALZ Bicep release has been downloaded, you will need to update `upstream-releases-version` within the environment variables file (.env) with the version number of the release that you just downloaded. For example, if you downloaded v0.16.5, you would update the file with the following:
 
     ```text
-    UPSTREAM_RELEASE_VERSION="v0.16.5"
+    UPSTREAM_RELEASE_VERSION="v0.16.6"
     ```
 
 1. You can now deploy the updated modules.