Merge branch 'main' into issue/625

Azure · Nov 1, 2023 · 6870e7b · 6870e7b
2 parents b3895fb + 0713a66
commit 6870e7b
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/.github/pester/release.tests.ps1 b/.github/pester/release.tests.ps1
@@ -42,7 +42,7 @@ Describe "version.json file tests" {
     }
 
     It "version.json file releaseNotes property has been updated and URL last split on / does not match the latest git tag" {
-      $releaseNotesUrlSplitLast | Should -Be $gitRepoLatestTag
+      $releaseNotesUrlSplitLast | Should -Not -Be $gitRepoLatestTag
     }
 
     It "version.json file releaseNotes property is a valid URL and has the correct format" {

diff --git a/.github/workflows/release-tests.yml b/.github/workflows/release-tests.yml
@@ -20,7 +20,7 @@ jobs:
 
       - name: Pester Tests
         id: pester
-        if: contains(github.head_ref, 'release')
+        if: startsWith(github.head_ref, 'release')
         uses: azure/powershell@v1
         with:
           inlineScript: |

diff --git a/docs/wiki/Accelerator.md b/docs/wiki/Accelerator.md
@@ -222,7 +222,7 @@ With the ALZ Accelerator framework, we have designed the pipelines and directory
     Here is an example of using the cmdlet to pull down version v0.16.5:
 
     ```powershell
-    Get-ALZGithubRelease -githubRepoUrl "https://github.com/Azure/ALZ-Bicep" -releases "v0.16.5" -directoryForReleases "C:\Repos\ALZ\accelerator\upstream-releases\"
+    Get-ALZGithubRelease -githubRepoUrl "https://github.com/Azure/ALZ-Bicep" -release "v0.16.6" -directoryForReleases "C:\Repos\ALZ\accelerator\upstream-releases\"
     ```
 
 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: