From 0bbccc5dc8aec9087cead030270f36aa39117a44 Mon Sep 17 00:00:00 2001 From: onevcat Date: Wed, 24 Jun 2026 18:07:07 +0900 Subject: [PATCH] docs: describe update install confirmation behavior Follow-up to #498: document that install-and-relaunch now requires an explicit confirmation, and that choosing Later cancels the attempt without permanently skipping the version. --- docs/components/updates.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/components/updates.md b/docs/components/updates.md index 6743c1f7..5634371b 100644 --- a/docs/components/updates.md +++ b/docs/components/updates.md @@ -17,6 +17,14 @@ Prowl uses the **Sparkle** framework for auto-updates. Releases are notarized. badge appears on the notification bell; clicking it opens the standard Sparkle dialog. - **On quit with a downloaded update:** Prowl offers to install or defer. +- **Install confirmation:** installing and relaunching always requires an + explicit confirmation. When an update is ready (or a user-initiated check finds + one already at the installing stage), Prowl shows an "Install Update and + Relaunch?" prompt. Choosing **Install and Relaunch** quits and relaunches to + finish; choosing **Later** cancels the current install attempt **without** + permanently skipping the version, so the same update is offered again on the + next check. A "Check for Updates" action will therefore never install and + relaunch on its own. ## Channels -- 2.51.2