Files
Groene AIandClaude Opus 5.5 6c0cfc1e2e Upgrade check: retry the GitHub releases page when it comes back short
`get_previous_release_tag` reads page 1 of the GitHub releases list and,
since #115228, refuses a page shorter than the 100 releases it asks for,
because choosing from or walking past a degraded page gave stale
baselines. It refused after a single request, though. GitHub sometimes
answers that request with HTTP 200 and `[]`, which `get_gh_api` returns
as a success (it retries only on HTTP errors), so one degraded answer
killed the job: on 2026-10-22, 14:58-15:32 UTC, `Upgrade check
(amd_release)` ended after about a minute with `Unknown job error` on 5
unrelated PRs. Probing the same URL returned `[]` on 4 of 19 requests,
each followed by a full page within 10-22 s; answers carry
`cache-control: s-maxage=60`, and one empty answer came from the edge
cache.

Retry a short first page up to 4 times, 60 s apart, so the cached answer
has expired before the next request, then raise the same
`ReleaseNotFoundException` as before. A full page still costs one request
and no wait. HTTP 5xx on the same request is left to #112974.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-22 16:07:21 +00:00
..
…
…
2026-09-30 17:29:19 +02:00
2026-10-04 07:54:08 +02:00
…