Repository navigation
fix(ci): retry release artifact fetches while the API catches up - #1576
Merged
Jeppe Fredsgaard Blaabjerg (jfblaa) merged 1 commit intoOct 5, 2026
Merged
Conversation
The verify step queries the artifact it just uploaded, and the REST API can return 404 for a few seconds after the upload finalizes. Retry the artifact lookups on 404 only, so other errors still fail immediately. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Oskar Haarklou Veileborg (BarrensZeppelin)
approved these changes
Oct 5, 2026
Jeppe Fredsgaard Blaabjerg (jfblaa)
deleted the
jfblaa/release-artifact-retry
branch
October 5, 2026 08:38
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
2 participants
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.
LLM Description written by Claude Code:claude-opus-5-5
The 1.4.2 publish run failed its first attempt at "Verify artifact transfer" with
gh: Not Found (HTTP 404). The step looked up the artifact about half a second after uploading it; the artifact exists with the expected ID and digest, the REST API just hadn't caught up yet.The shared verify/download script now retries the artifact lookups on HTTP 404 (6 attempts, 5s apart). Any other error still fails immediately, and the metadata and digest checks are unchanged.
🤖 Generated with Claude Code
Note
Low Risk
CI-only change to artifact download retries; no application or publish credential logic is modified.
Overview
Fixes flaky Verify artifact transfer / Download verified tarballs failures when
gh apireturns HTTP 404 right after an artifact upload.The shared
download-verified-tarballsscript now uses afetch_artifacthelper that retries artifact metadata and zip downloads up to 6 times with 5s backoff, but only when stderr indicates HTTP 404. Any other API error still fails immediately; the existing metadata, digest, and tarball validation logic is unchanged.Because the step is YAML-anchored, both the verify and publish jobs get the same retry behavior.
Reviewed by Cursor Bugbot for commit 2efd6ee. Configure here.