ci: add concurrency groups to scheduled/update workflows (#3551)

Fixes #3547

Without a concurrency group, a new scheduled run starts even if the
previous one is still in progress, wasting runner minutes. Follows the
pattern from #3536 which added concurrency to functions.yaml.

Author: Ankitsinghsisodya

.github/workflows/test-podman-next.yaml

@@ -7,6 +7,10 @@ on:
   schedule:
     - cron: '0 2 * * *'
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   test:
     name: Podman Next Test

.github/workflows/update-builder.yaml

@@ -5,6 +5,10 @@ on:
     - cron: '0 * * * *'
   workflow_dispatch:
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   build-and-push-image:
     permissions:

.github/workflows/update-ca-bundle.yaml

@@ -9,6 +9,10 @@ on:
     - cron: '0 */4 * * *'
   workflow_dispatch:
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   update:
     name: Update CA bundle

.github/workflows/update-python-platform.yaml

@@ -9,6 +9,10 @@ on:
     - cron: "0 6 * * *" # Daily at 06:00.
   workflow_dispatch: # Manual workflow trigger
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   update:
     name: Update func-python version

.github/workflows/update-quarkus-platform.yaml

@@ -9,6 +9,10 @@ on:
     - cron: '0 */4 * * *'
   workflow_dispatch:
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   update:
     name: Update Quarkus Platform

.github/workflows/update-springboot-platform.yaml

@@ -9,6 +9,10 @@ on:
     - cron: '0 */4 * * *'
   workflow_dispatch:
 
+concurrency:
+  group: ${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
 jobs:
   update:
     name: Update Spring Boot Platform