From e5fd3246e6f357271374629a8f9c2c9bd99e3b78 Mon Sep 17 00:00:00 2001 From: rivassec Date: Sat, 10 Oct 2026 12:07:52 -0700 Subject: [PATCH] ci: accept 503 in the deploy link check github.com has returned 503 to Actions runners for /blob/ URLs for hours, blocking every deploy although the links are fine (200 from elsewhere). 404s still fail; the weekly link-rot workflow keeps its strict accept list. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01JoTNmbmc8o4TJDUGG2gd3P --- .github/workflows/deploy.yml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml index 4dc7a9fb..aeb35eeb 100644 --- a/.github/workflows/deploy.yml +++ b/.github/workflows/deploy.yml @@ -89,6 +89,11 @@ jobs: # URL exclusions live in .lycheeignore (single source of truth, shared # with the weekly link-rot workflow; lychee reads it automatically). # Path exclusions stay inline: .lycheeignore holds URL patterns only. + # 503 is accepted because github.com throttles Actions runners on + # /blob/ pages for hours at a time (2026-10-10: every deploy blocked + # while the same URLs returned 200 elsewhere). A 503 says nothing + # about whether a link is broken, so it must not block a deploy; + # 404s still fail, and the weekly link-rot job still reports 503s. uses: lycheeverse/lychee-action@e7477775783ea5526144ba13e8db5eec57747ce8 # v2.9.0 with: args: >- @@ -96,7 +101,7 @@ jobs: --base https://rivassec.com --remap "https://rivassec.com/ file://${{ github.workspace }}/output/" --verbose - --accept 200..=299,429 + --accept 200..=299,429,503 --max-retries 5 --retry-wait-time 2 --exclude-path output/feeds