fix: clear version check cache on channel switch to avoid stale notifications

Author: BYK

src/lib/db/release-channel.ts

@@ -11,6 +11,7 @@
 
 import { getDatabase } from "./index.js";
 import { runUpsert } from "./utils.js";
+import { clearVersionCheckCache } from "./version-check.js";
 
 const KEY = "release_channel";
 
@@ -37,11 +38,19 @@ export function getReleaseChannel(): ReleaseChannel {
 /**
  * Persist the release channel.
  *
+ * If the channel has changed, the cached version-check result is also cleared
+ * so the next notification does not display a stale version from the old channel
+ * (e.g. a cached stable version labelled as a nightly update after switching).
+ *
  * @param channel - Channel to store
  */
 export function setReleaseChannel(channel: ReleaseChannel): void {
   const db = getDatabase();
+  const current = getReleaseChannel();
   runUpsert(db, "metadata", { key: KEY, value: channel }, ["key"]);
+  if (channel !== current) {
+    clearVersionCheckCache();
+  }
 }
 
 /**

src/lib/db/version-check.ts

@@ -38,6 +38,22 @@ export function getVersionCheckInfo(): VersionCheckInfo {
   };
 }
 
+/**
+ * Clear the cached latest version.
+ *
+ * Should be called when the release channel changes so that stale version
+ * data from the previous channel is not shown in update notifications.
+ * The last-checked timestamp is also reset so a fresh check is triggered
+ * on the next CLI invocation.
+ */
+export function clearVersionCheckCache(): void {
+  const db = getDatabase();
+  db.query("DELETE FROM metadata WHERE key = ? OR key = ?").run(
+    KEY_LAST_CHECKED,
+    KEY_LATEST_VERSION
+  );
+}
+
 /**
  * Store the version check result.
  * Updates both the last checked timestamp and the latest known version.