wtclaude
188e6eb882
All checks were successful
PR Checks / rust-gates (pull_request) Successful in 1m32s
Run 75 built every artifact, pushed tag v0.1.1, then took a 500 from POST /releases one second later and exited 22. The tag was left orphaned with no release and no binaries, so the handoff fix in #22 reached no operator until the workflow was re-run by hand today. Re-running published the same four assets untouched, via the orphan-tag recovery the plan step already has. So the 500 was a race with the tag push -- Gitea had not finished processing the pushed tag when the POST arrived -- and not a bad request. Two separate gaps made that worse than it needed to be. `curl -sSf` prints no response body on an error status. All the log carried was "curl: (22) ... error: 500", so the cause had to be inferred from timestamps rather than read. Every call in this step now captures the body and prints it on failure, including the asset uploads. And nothing retried. The plan step can recover an orphan tag, but only on a run that reaches it, and a later push with no releasable commits stands down before it gets there -- which is why this one sat until someone looked. The POST now retries five times with a 5/10/15/20s backoff. 4xx is deliberately not retried: a bad token or a malformed body will not improve by being sent again, and retrying would turn a clear failure into a slow one. A give-up message names the orphan tag and says a re-run republishes. The asset uploads get the same treatment, because a release whose SHA256SUMS does not cover every binary it advertises is worse than no release -- that file is the trust anchor for an unsigned download. Verified by extracting the step's shell from the YAML and running the loop against a stubbed curl: first-try success, 500-then-success (the case that actually happened), two 500s then success, five 500s giving up, 403 and 404 aborting without retrying, and a 000 network failure being retried. bash -n clean and the YAML parses. Typed ci(...) rather than fix(...) on purpose: the plan step bumps on feat/fix, and this changes no binary, so a release here would be an empty one. Co-Authored-By: Claude <noreply@anthropic.com>