@retasc/cli 1.43.0 → 1.44.0

package/CHANGELOG.md

@@ -6,6 +6,20 @@ release commits and the issues they reference.
 
 Dates are the npm publish date. Each entry names the RTSC issue behind it.
 
+## 1.44.0 (2026-09-08)
+
+- **RTSC-861** — the proxy now tells Retasc which CLI version it is. It rides on
+  `mint_session_key`, the one call every proxy already makes at startup, as an optional
+  `cliVersion` argument, so an older build that sends nothing still mints exactly as
+  before.
+
+  Why it matters: the update notice (RTSC-520) fires from a `postAction` hook on
+  `retasc <command>`, and someone whose only contact with the CLI is the proxy their
+  harness spawns runs no commands and never sees it. Three live setups were found on
+  builds older than 1.41.0 with no way to find out. The server can now say so in the
+  tool result, which reaches every harness, and with this version it can name the exact
+  gap instead of inferring one from behaviour.
+
 ## 1.43.0 (2026-09-05)
 
 - **RTSC-799** - `tidy`, `done` and `claim` now work out which branch is this repo's trunk

package/dist/lib/session.js

@@ -46,7 +46,13 @@ export async function mintSessionKey(opts) {
                     jsonrpc: "2.0",
                     id: MINT_RPC_ID,
                     method: "tools/call",
-                    params: { name: "mint_session_key", arguments: { label: opts.label } },
+                    params: {
+                        name: "mint_session_key",
+                        arguments: {
+                            label: opts.label,
+                            ...(opts.cliVersion ? { cliVersion: opts.cliVersion } : {}),
+                        },
+                    },
                 }),
                 signal: AbortSignal.timeout(MINT_TIMEOUT_MS),
             });

package/dist/proxy.js

@@ -15,6 +15,7 @@ import { AUTO_WORKSPACE, resolveConn } from "./lib/keystore.js";
 import { toolResult as parseTool } from "./lib/toolresult.js";
 import { mintSessionKey, appendFallbackNotice, recordSession, nameWorkspace, RPC_ID } from "./lib/session.js";
 import { readHookRecord, clearHookRecord, modelFromTranscript } from "./lib/sessionHook.js";
+import { VERSION } from "./version.js";
 import { attachRoot, isLocalAttachCall, mergeAttachTool, readAttachFile, resolveAttachPath, uploadFailureMessage, uploadUrlWith, } from "./lib/attachFile.js";
 import { MAX_FETCH_BYTES, downloadFailureMessage, existingDownload, isLocalFetchCall, mergeFetchTool, resolveDownloadTarget, writeDownloadedFile, } from "./lib/fetchFile.js";
 // RTSC-92/98: resolve the workspace key via the SHARED resolver, so the proxy and
@@ -195,7 +196,16 @@ async function adoptSessionKey() {
     if (!KEY)
         return;
     const label = process.env.RETASC_SESSION_LABEL || `${hostname()}#${process.pid}`;
-    const outcome = await mintSessionKey({ url: MCP_URL, key: KEY, label, warn: log });
+    // RTSC-861 — report our own version at the one call every proxy makes at startup,
+    // so the server never has to infer whether this build is current. A proxy too old to
+    // send it is exactly the case the server-side inference exists for.
+    const outcome = await mintSessionKey({
+        url: MCP_URL,
+        key: KEY,
+        label,
+        cliVersion: VERSION,
+        warn: log,
+    });
     if (outcome.ok) {
         activeKey = outcome.key; // switch to the session key
         log(`adopted session key "${outcome.session ?? label}"`);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@retasc/cli",
-  "version": "1.43.0",
+  "version": "1.44.0",
   "description": "Retasc CLI — the issue tracker AI agents pull work from. Sign in with GitHub or Google, create projects, mint agent API keys, and wire your agent to the Retasc MCP server in one command.",
   "type": "module",
   "bin": {