Release Failed for v0.21.11 on 2026-08-13

[github-actions]

The release workflow failed.

Release tag: v0.21.11
Run: https://github.com/QwenLM/qwen-code/actions/runs/31665796236

Failed job(s):

• quality

[qwen-code-dev-bot]

🤖 Withdrawing the claim above — the automated fix attempt did not succeed; no further automated attempts will be made on this issue.

What the agent found, in case it helps a human contributor:

Qwen failed during develop-issue: timeout (3000000ms).

See the Qwen Autofix agent step logs for model/tool output.

[doudouOUC]

Diagnosed this one — it was a flaky test, not a product regression, and the release recovered on its own.

Root cause. The quality job failed in Run Workspace Tests on packages/webui/src/daemon/session/DaemonSessionProvider.test.tsx — the test keeps the current attachment live while a same-session load/reload fails asserted ['A transcript', ' still live'] but observed only ['A transcript']. The test asserts transcript state mid-stream and relies on the flushTranscriptDispatch() helper to drain the batched transcript dispatch. That helper used a single setTimeout(0) hop: the dispatch timer and the helper's timer are registered from concurrently-draining microtask chains, so their registration order is unspecified, and Node drains microtasks between timer callbacks. A single hop registered first can resume the test — and its assertion — before the dispatch timer fires, so the ' still live' chunk had not been applied yet.

Why it is a flake, not a regression. The release was re-run (attempt 2) on the exact same head SHA (abfd4436) and passed, and v0.21.11 published successfully. Same code, different outcome → non-deterministic timing race. The autofix agent timed out trying to chase it, which is why this was left un-diagnosed.

Already addressed on main. #9058 (commit 52cfb1897) hardened flushTranscriptDispatch() to use two chained timer hops (with a comment explaining the ordering guarantee), and #8982 further reduced ENOSPC / load-sensitive flakes. No product change is needed and no further action is required here — leaving closure to a maintainer since this was filed by the release workflow.