Skip to content

Commit 87c7f00

Browse files
committed
fix(ci): retry Pages deployment once on transient failure
The Pages backend intermittently rejects deployments with a generic 'Deployment failed, try again later'. Both workflow_run-triggered deploys so far (the post-release appcast publishes for v1.16.1 and v1.17.0) hit this, leaving the live appcast stale so Sparkle stopped offering the new release until an unrelated push redeployed the site. A manual rerun of the identical job succeeds, so retry once in-job after a 60 second pause before failing the run.
1 parent 980485d commit 87c7f00

1 file changed

Lines changed: 16 additions & 1 deletion

File tree

.github/workflows/website.yml

Lines changed: 16 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,8 +62,23 @@ jobs:
6262
runs-on: ubuntu-latest
6363
environment:
6464
name: github-pages
65-
url: ${{ steps.deployment.outputs.page_url }}
65+
url: ${{ steps.deployment.outputs.page_url || steps.deployment-retry.outputs.page_url }}
6666
steps:
6767
- name: Deploy
6868
id: deployment
69+
continue-on-error: true
70+
uses: actions/deploy-pages@v5
71+
72+
# The Pages backend intermittently rejects deployments with a generic
73+
# "Deployment failed, try again later". When that hits the post-release
74+
# workflow_run deploy, the appcast silently goes stale and Sparkle stops
75+
# offering updates until an unrelated push redeploys the site. Retry once
76+
# after a pause before failing the run.
77+
- name: Wait before retry
78+
if: steps.deployment.outcome == 'failure'
79+
run: sleep 60
80+
81+
- name: Retry deploy
82+
id: deployment-retry
83+
if: steps.deployment.outcome == 'failure'
6984
uses: actions/deploy-pages@v5

0 commit comments

Comments
 (0)