Skip to content

ci: accept 503 in the deploy link check - #93

Merged
rivassec merged 1 commit into
mainfrom
ci/lychee-accept-503
Oct 10, 2026
Merged

rivassec merged 1 commit into
mainfrom
ci/lychee-accept-503

Conversation

@rivassec

Copy link
Copy Markdown
Owner

github.com has been returning 503 to Actions runners for /blob/ URLs for hours (7 links, all 200 when fetched from elsewhere), so every deploy fails at lychee and #91's change never reached the site.

  • deploy.yml: add 503 to lychee's --accept. 404s and other errors still fail the build.
  • link-rot.yml is unchanged, so a 503 that persists still shows up in the weekly report.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JoTNmbmc8o4TJDUGG2gd3P

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 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JoTNmbmc8o4TJDUGG2gd3P
@rivassec
rivassec merged commit d5ad544 into main Oct 10, 2026
20 checks passed
@rivassec
rivassec deleted the ci/lychee-accept-503 branch October 10, 2026 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant