From b909d53efbbbc4304bca41557c869907f45de46b Mon Sep 17 00:00:00 2001
From: "CanbiZ (MickLesk)" <47820557+MickLesk@users.noreply.github.com>
Date: Thu, 23 Apr 2026 13:39:36 +0200
Subject: [PATCH] fix(twingate-connector): perform real apt upgrade during
 update flow

The update path used ensure_dependencies, which only installs missing
packages and does not upgrade already installed ones. As a result, users
could see 'Updated successfully' even when a newer twingate-connector
version was available.

Switch update_script to a real package update flow:
- ensure apt is healthy
- refresh apt metadata
- install/upgrade twingate-connector via retry helper
- restart service

This aligns behavior with Twingate's documented upgrade process.
---
 ct/twingate-connector.sh | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/ct/twingate-connector.sh b/ct/twingate-connector.sh
index 1c662686b..5fd4bb2c7 100644
--- a/ct/twingate-connector.sh
+++ b/ct/twingate-connector.sh
@@ -30,7 +30,12 @@ function update_script() {
   fi
 
   msg_info "Updating ${APP}"
-  ensure_dependencies twingate-connector
+  ensure_apt_working || return 100
+  $STD apt update || msg_warn "apt update failed, continuing with cached package lists"
+  install_packages_with_retry twingate-connector || {
+    msg_error "Failed to update ${APP} package"
+    return 100
+  }
   $STD systemctl restart twingate-connector
   msg_ok "Updated successfully!"
   exit