From b000e05b117b0d51c5eed1bec9b671edec82a230 Mon Sep 17 00:00:00 2001 From: yoniebans Date: Mon, 8 Jun 2026 13:59:31 +0200 Subject: [PATCH] fix(desktop): don't claim the backend update succeeded when it never returns MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The no-return error said 'Backend updated but did not come back online' — but once the connection drops the client can't know the update's exit code, only that it was started and the backend is unreachable. Reword to not overclaim: the update may not have completed. --- apps/desktop/src/store/updates.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/desktop/src/store/updates.ts b/apps/desktop/src/store/updates.ts index cc64f4822f6..9365690a370 100644 --- a/apps/desktop/src/store/updates.ts +++ b/apps/desktop/src/store/updates.ts @@ -336,7 +336,7 @@ function finishBackendApply(returned: boolean): DesktopUpdateApplyResult { applying: false, stage: 'error', error: 'apply-failed', - message: 'Backend updated but did not come back online. Check the backend host.' + message: 'Backend didn’t come back online. The update may not have completed — check the backend host.' }) return { ok: false, error: 'apply-failed', message: 'Backend did not come back online.' }