From 32e0057badd92043ad9a7687aab762c890c899d0 Mon Sep 17 00:00:00 2001 From: Qiufeng Date: Fri, 11 Sep 2026 08:11:27 +0800 Subject: [PATCH] fix: set operation to apply when staging update completes downloadAndStageUpdate set status=staged but left operation=download, causing the root runner CLI to reject the apply (operation check failed) and silently skip the version switch. The symlink stayed on the old version while the runner reported SUCCESS. release: 1.3.2 --- package.json | 2 +- server/update-service.ts | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/package.json b/package.json index 6e0a8fe..60bdef9 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "tallynote", - "version": "1.3.1", + "version": "1.3.2", "private": true, "type": "module", "packageManager": "pnpm@9.0.6", diff --git a/server/update-service.ts b/server/update-service.ts index a0c6e8f..b4afd06 100644 --- a/server/update-service.ts +++ b/server/update-service.ts @@ -765,7 +765,7 @@ export async function downloadAndStageUpdate( // Transition to staged const staged = database.prepare( - "UPDATE update_jobs SET status='staged', actual_sha256=?, size_bytes=?, download_path=?, updated_at=? WHERE id=? AND status IN ('verifying', 'downloading')", + "UPDATE update_jobs SET status='staged', operation='apply', actual_sha256=?, size_bytes=?, download_path=?, updated_at=? WHERE id=? AND status IN ('verifying', 'downloading')", ).run(downloaded.sha256, downloaded.size, workspace, Date.now(), jobId); if (staged.changes !== 1) return; // cancelled