mirror of
https://github.com/QwenLM/qwen-code.git
synced 2026-11-07 06:19:43 -10:00
0371b40fbd
* fix(release): retry transient standalone runtime downloads (#11870) The v0.23.4 publish died in Build Standalone Archives while the identical re-run — same commit, same prebuild artifact — passed, so the failure was a transient external call, not a code defect. That leg downloads SHASUMS256.txt plus one Node.js archive per target with no timeout and no retry, so a single nodejs.org blip aborted the whole release. Bound each download with a 120s fetch timeout and retry up to 3 times with exponential backoff, verifying the archive checksum inside the loop so a corrupted download is re-fetched rather than reported once and abandoned. Co-authored-by: Qwen-Coder <[email protected]> * fix(release): harden runtime download retries and pin their wiring (#11870) Address review findings on the retry change. Verify each flavor's checksum list inside the retry, so a corrupt or truncated SHASUMS256.txt is re-downloaded instead of poisoning every archive check against a stale in-memory map; the expected names come from the same runtimeArchiveName helper the archive leg uses, so the two cannot drift. Drop the timeoutMs/maxAttempts knobs no caller could set and read the module constants directly, matching uploadWithRetry. Include error.cause in retry warnings, since a real undici failure reads only "fetch failed", and separate the retry notice from the error text. Pin the retry call sites, backoff schedule, and constant values in tests, and drop the nodejs.org host attribution from the rationale comment: the v0.23.4 abort was a transient download failure and the retry is host-agnostic. Co-authored-by: Qwen-Coder <[email protected]> * fix(release): aggregate missing runtime checksums under the display label (#11870) * test(release): pin bun checksum label and observe retry wiring behaviourally (#11870) Co-authored-by: Qwen-Coder <[email protected]> * test(release): pin archive-leg call site and tolerate comments in wiring pin (#11870) Co-authored-by: Qwen-Coder <[email protected]> --------- Co-authored-by: qwen-code-dev-bot <[email protected]> Co-authored-by: Qwen-Coder <[email protected]>