ci(docs): exclude flaky istio.io from lychee link check - #483
Merged
Conversation
`https://istio.io/latest/docs/reference/config/security/authorization-policy/` (cited in ADR-0022) intermittently refuses connections from GitHub runners — it returns 200 from a normal client (verified: 0.6s, HTTP 200). It failed the lychee gate on the v0.36.84 release PR (#482) and timed out earlier this cycle. Excluded the host, matching the existing precedent for public.cyber.mil. The link is valid; this only stops a live external host's runner-side flakiness from blocking merges. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Destynova2
enabled auto-merge (squash)
July 28, 2026 06:31
Merged
Destynova2
added a commit
that referenced
this pull request
Jul 28, 2026
## 🤖 New release * `grob`: 0.36.84 -> 0.36.85 <details><summary><i><b>Changelog</b></i></summary><p> <blockquote> ## [0.36.85](v0.36.84...v0.36.85) - 2026-07-28 ### Fixed - *(openai)* preserve tool-result images on the Responses (Codex) path ([#488](#488)) ### Other - *(docs)* exclude flaky istio.io from lychee link check ([#483](#483)) </blockquote> </p></details> --- This PR was generated with [release-plz](https://github.com/release-plz/release-plz/).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The lychee (broken-link) gate failed on the v0.36.84 release PR (#482):
The link is not broken — it returns
200from a normal client (verified:0.6s, HTTP 200). istio.io intermittently refuses connections from GitHub runner
IPs; the same URL timed out earlier this release cycle too.
Fix
Added the host to
.lycheeignore, matching the existing precedent forpublic.cyber.mil(excluded for the identical "flaky from runners, not broken"reason). The link stays in the doc; only the runner-side flakiness stops blocking
merges.
It was non-blocking for v0.36.84 (lychee isn't a Required check, so the release
went through), but it turns the docs-lint workflow red on every run that
re-checks that URL.
🤖 Generated with Claude Code