From 99a6debd3aa6ddd0daf6b366abce4395d01a3ecb Mon Sep 17 00:00:00 2001 From: rcourtman Date: Tue, 2 Dec 2025 03:03:51 +0000 Subject: [PATCH] fix: Update Channel setting not persisting after save The Update Channel dropdown reverted to "stable" after saving because the frontend was overwriting the user's saved preference with the running version's channel. Now the saved setting takes priority over the detected channel. Related to #738 --- frontend-modern/src/components/Settings/Settings.tsx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/frontend-modern/src/components/Settings/Settings.tsx b/frontend-modern/src/components/Settings/Settings.tsx index dbe65b9..6a175fb 100644 --- a/frontend-modern/src/components/Settings/Settings.tsx +++ b/frontend-modern/src/components/Settings/Settings.tsx @@ -2040,7 +2040,9 @@ const Settings: Component = (props) => { setVersionInfo(version); // Also set it in the store so it's available globally updateStore.checkForUpdates(); // This will load version info too - if (version.channel) { + // Only use version.channel as fallback if user hasn't configured a preference + // The user's saved updateChannel preference should take priority + if (version.channel && !systemSettings.updateChannel) { setUpdateChannel(version.channel as 'stable' | 'rc'); } } catch (error) {