Ensure concurrency control for canary and release workflows (#3243)

ci: Ensure concurrency control for canary and release workflows

- Added concurrency configuration to `porter-canary.yml` to prevent multiple canary releases from running simultaneously.
- Added concurrency configuration to `porter-release.yml` to prevent multiple releases from running simultaneously.

Signed-off-by: Kim Christensen <kimworking@gmail.com>

.github/workflows/porter-canary.yml

@@ -4,6 +4,15 @@ on:
     branches:
       - main
       - release/*
+
+# This configuration ensures that multiple canary releases don't run at the same time:
+# - The 'group' combines the workflow name and git reference to create a unique identifier
+# - 'cancel-in-progress: false' means if a new release is triggered, it will wait in line
+#   instead of canceling any running release
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: false
+
 jobs:
   build_pipelinesrelease_template:
     name: build_pipelinesrelease_template

.github/workflows/porter-release.yml

@@ -6,6 +6,14 @@ on:
     - "!latest*"
     - "!canary*"
 
+# This configuration ensures that multiple releases don't run at the same time:
+# - The 'group' combines the workflow name and git reference to create a unique identifier
+# - 'cancel-in-progress: false' means if a new release is triggered, it will wait in line
+#   instead of canceling any running release
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: false
+
 jobs:
   build_pipelinesrelease_template:
     name: build_pipelinesrelease_template