Skip to content

Commit b3c0433

Browse files
btraversclaude
andcommitted
ci: drop workflow_dispatch and collapse duplicate release deploys
Address review: - Remove workflow_dispatch. It defaults to running on main, which would deploy *unreleased* docs to production — reintroducing the problem this change fixes. A failed Pages deploy can be re-run via GitHub's "Re-run jobs" on the release run, which keeps the release tag's commit as the checkout context. - Set concurrency cancel-in-progress: true so a version bump that publishes several Releases at once (each firing release: published for the same commit) collapses into a single Pages deploy instead of N identical ones. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 455ac63 commit b3c0433

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

.github/workflows/deploy-docs.yml

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,21 +1,21 @@
11
name: Deploy Documentation
22

33
# Publish docs when a version is released (changesets creates a GitHub Release on publish), so the
4-
# site documents the latest *released* library rather than every commit on main. `workflow_dispatch`
5-
# is a manual redeploy escape hatch for docs-only fixes between releases.
4+
# site documents the latest *released* library rather than every commit on main.
65
on:
76
release:
87
types: [published]
9-
workflow_dispatch:
108

119
permissions:
1210
contents: read
1311
pages: write
1412
id-token: write
1513

1614
concurrency:
15+
# A version bump can publish several Releases at once (monorepo); collapse that burst of events
16+
# for the same commit into a single Pages deploy — the latest run cancels earlier ones.
1717
group: pages
18-
cancel-in-progress: false
18+
cancel-in-progress: true
1919

2020
env:
2121
FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: true

0 commit comments

Comments
 (0)