From 770ca1d02650abdf537129fbbb86a97e26628544 Mon Sep 17 00:00:00 2001 From: Musiker15 Date: Wed, 16 Sep 2026 19:17:49 +0200 Subject: [PATCH] ci: run deploys one at a time Merging several PRs back to back started parallel deploys into the same DocumentRoot. One run's post-deploy step moved csp-hashes.conf while another run still needed it, so two of six runs on 16.09. failed. A concurrency group now queues them. Running deploys are not cancelled, an interrupted upload would leave a half-updated site. --- .github/workflows/deploy.yml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 37cad89..362984c 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -13,6 +13,15 @@ permissions: # instead of stuck-on-pending. statuses: write +# Only one deploy at a time. Parallel runs upload into the same DocumentRoot, +# and the post-deploy step of one run moves the csp-hashes.conf the other run +# still needs. A newer push waits for the running deploy instead of cancelling +# it, because an interrupted upload would leave a half-updated site. GitHub +# keeps just the newest waiting run, so the site always ends on the latest commit. +concurrency: + group: deploy-docs + cancel-in-progress: false + jobs: build-and-deploy: name: Build & Deploy