From 020a00d909ba0d33e2512ff65371a177b7e2838d Mon Sep 17 00:00:00 2001
From: Max Isbey <224885523+maxisbey@users.noreply.github.com>
Date: Fri, 2 Oct 2026 16:48:06 +0000
Subject: [PATCH] Let a newer Deploy Docs run cancel the one in progress

A run that never gets a runner held the deploy-docs concurrency group, so
every later deploy waited behind it and the site went stale. Each run builds
the tips of main and v1.x, so the newest run publishes everything.
---
 .github/workflows/deploy-docs.yml | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/.github/workflows/deploy-docs.yml b/.github/workflows/deploy-docs.yml
index 3254ca4a24..5f81a8c545 100644
--- a/.github/workflows/deploy-docs.yml
+++ b/.github/workflows/deploy-docs.yml
@@ -26,7 +26,12 @@ on:
 
 concurrency:
   group: deploy-docs
-  cancel-in-progress: false
+  # Newest run wins. build-docs.sh builds the tips of main and v1.x, not the
+  # triggering commit, so a newer run publishes everything an older one would,
+  # and Pages takes the site as one artifact, so a cancelled run leaves the live
+  # site as it was. With `false`, a run that never gets a runner holds the group
+  # and every later deploy waits behind it.
+  cancel-in-progress: true
 
 jobs:
   deploy-docs: