workshopsoft/ludic
2
0
Fork 0
Code Issues Pull requests Projects Releases 26 Packages Wiki Activity Actions
ludic/changes/docs-deploy-concurrency.md
Orkuncakilkaya f81ca5c3c1
All checks were successful
bootstrap / cfree-fixpoint (push) Successful in 25s
Details
ci / build-and-test (push) Successful in 2m54s
Details
commit-lint / conventional-commits (push) Successful in 5s
Details
docs / build-and-deploy (push) Successful in 32s
Details
ci(docs): serialise the pages deploy 
Publishing the site force-pushes an orphan `pages` branch. Two runs racing can
therefore land out of order and leave `pages` holding the older build, with both
runs green and nothing to indicate the site went backwards.

A `pages-deploy` concurrency group with cancel-in-progress makes a newer push
cancel an older in-flight build rather than queue behind it, so the last push to
land is the one that ends up published.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-09-05 03:37:33 +03:00

376 B
Raw Blame History

bump: patch type: ci The docs deploy is serialised. Publishing is a force-push of an orphan pages branch, so two runs racing could land out of order and leave the site holding the older build — with both runs reporting success. A pages-deploy concurrency group with cancel-in-progress means a newer push cancels an older in-flight build instead of queueing behind it.