@quantiya/codevibe 1.0.51 → 1.0.52

package/bin/codevibe

@@ -214,8 +214,12 @@ do_update() {
     echo -e "${YELLOW}!${NC} claude CLI not found — skipping Claude Code plugin update"
     echo ""
     echo -e "${BOLD}Updated versions:${NC}"
-    show_version
-    return 0
+    # Same in-place-update gotcha as the success path — `exec "$0" version`
+    # re-runs the just-installed script bytes instead of the OLD in-memory
+    # show_version that was loaded before npm overwrote us. This branch
+    # also returns 0, so swapping `show_version + return 0` for `exec`
+    # preserves exit semantics.
+    exec "$0" version
   fi
 
   echo ""
@@ -299,9 +303,16 @@ do_update() {
 
   echo ""
 
-  # Show new versions
+  # Show new versions.
+  # `exec "$0" version` re-runs the (now-updated-on-disk) script in a fresh
+  # bash process, so the post-update output reflects the JUST-INSTALLED
+  # version's `show_version`, not the OLD function definitions that this
+  # bash process loaded into memory BEFORE `npm install -g` overwrote the
+  # script on disk. Without this, an upgrade like 1.0.50 → 1.0.51 displays
+  # the old script's versions block (e.g. missing a freshly-added plugin)
+  # even though the new bytes are already installed.
   echo -e "${BOLD}Updated versions:${NC}"
-  show_version
+  exec "$0" version
 }
 
 # ─── Command routing ─────────────────────────────────────────────────

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@quantiya/codevibe",
-  "version": "1.0.51",
+  "version": "1.0.52",
   "description": "CodeVibe — Control Claude Code, Gemini CLI, Codex CLI, and Antigravity CLI from your iPhone and Android. Real-time sync, voice prompts, approve file edits, E2E encrypted.",
   "bin": {
     "codevibe": "./bin/codevibe",