Repository navigation
ci(windows): track remaining Release Windows check product failures #3377
Description
Activity
Current-status correction for this routing tracker (2026-08-21):
- fix(desktop): drain untracked Runtime Host before update #3382 merged and closed windows: auto-update silently fails when a Runtime Host process survives the app quit (installer cannot clear it) #3340. Exact-head Windows gates now pass the Runtime Host update handoff; treat old ProductVersion + surviving candidate as a fix(desktop): drain untracked Runtime Host before update #3382 regression rather than an open primary blocker.
- fix(desktop): clear registered Runtime Host residue before update handoff #3348 is closed and intentionally retired; its raw-PID approach remains historical only.
- feat(win): Abort-path installer rollback with backup retention #3265 exact head
68520adchas CI, audit, autoupdate, and expanded rollback L3 green (Windows run 32477989412); it is waiting for independent human review. - runtime-host: intermittent 'stopped responding during startup' after a Windows upgrade over an existing profile #3279 remains the primary open product fault: intermittent
host_unresponsive/ renderer-never-mounted startup, including fresh isolated profiles. - test(windows): harden the release-verification harness and pin its contracts #3327 remains the owner only for harness deadline/observation/cleanup regressions.
Suggested body update: replace the stale relationship table and leave this tracker open until #3265 is reviewed and #3279 is independently reproduced/resolved. After that, close this cross-cutting router and keep future failures in their single owning issue.
中文同步：#3382 已合并并关闭 #3340，#3348 已退役；#3265 当前 head 的所有自动门禁全绿、待人工复审；#3279 是目前唯一主要的开放产品启动故障。建议 issue owner 按此更新正文关系表。
Closing this router, since its own close condition is now met. #3327 and #3382 merged, #3265 merged on 2026-08-23, and #3348 was retired, which leaves #3279 as the single remaining Windows startup fault and #2142 as the roadmap. Any later Windows release failure can now be filed against whichever of those owns it, so a cross-cutting tracker no longer adds routing. Please reopen if a failure turns up that has no single owning issue.
English
Purpose
#3327 made the Windows release verifier bounded and attributable without hiding product failures. This issue routes the remaining Windows release failures to one owner and stays open only while the current cross-cutting work is unresolved.
Current status
ProductVersion, surviving candidate, or busy install directory is a regression against this fix.host_unresponsiveand renderer-never-mounted startup failures on Windows, including fresh isolated profiles.Triage
Runtime Host stopped responding during startup,host_unresponsive, or a renderer that never mounts: runtime-host: intermittent 'stopped responding during startup' after a Windows upgrade over an existing profile #3279.Close when
简体中文
目的
#3327 已经让 Windows release verifier 具备明确边界并能够提供可归因的证据，同时不会隐藏真实产品故障。本 issue 只负责把剩余 Windows release 失败分流到唯一责任项，并在当前跨问题工作收敛后关闭。
当前状态
ProductVersion、残留 candidate 或安装目录被占用再次出现时，应视为该修复的回归。host_unresponsive和 renderer 始终未挂载问题，包括全新隔离 profile。分流规则
Runtime Host stopped responding during startup、host_unresponsive或 renderer 始终未挂载：归 runtime-host: intermittent 'stopped responding during startup' after a Windows upgrade over an existing profile #3279。关闭条件
AI disclosure: OpenAI Codex updated and translated this maintainer-directed tracker after verifying the linked issues, pull requests, and current check state.