Scheduled and update workflows have no concurrency configuration, so if a scheduled run is still in progress when the next one fires, both run simultaneously — wasting runner minutes and potentially causing race conditions on PRs they create.
This was addressed for functions.yaml in #3536, but the following workflows still lack it:
test-podman-next.yamlupdate-builder.yamlupdate-python-platform.yamlupdate-quarkus-platform.yamlupdate-springboot-platform.yamlupdate-ca-bundle.yaml
Proposed fix: add a concurrency block (e.g. group: ${{ github.workflow }}-${{ github.ref }}, cancel-in-progress: true) to each workflow, matching the pattern from functions.yaml.
Scheduled and update workflows have no
concurrencyconfiguration, so if a scheduled run is still in progress when the next one fires, both run simultaneously — wasting runner minutes and potentially causing race conditions on PRs they create.This was addressed for
functions.yamlin #3536, but the following workflows still lack it:test-podman-next.yamlupdate-builder.yamlupdate-python-platform.yamlupdate-quarkus-platform.yamlupdate-springboot-platform.yamlupdate-ca-bundle.yamlProposed fix: add a
concurrencyblock (e.g.group: ${{ github.workflow }}-${{ github.ref }},cancel-in-progress: true) to each workflow, matching the pattern fromfunctions.yaml.