You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 23ae573
Browse filesBrowse the repository at this point in the historyBrowse files
fix(cli): compare t3 update against the installed service, not the executable
A newer t3 downloaded by hand and pointed at a home whose service still
ran the old version reported "already on" and did nothing, because the
already-on and downgrade checks compared the target against the
executable's own version. The installed service version is what the
machine runs, so it is now the baseline whenever a service is installed
for the target home; the executable's version only stands in when there
is no service.
Co-Authored-By: Claude Fable 5 <[email protected]>
reason: `t3@${targetVersion} is published on npm only. Install it with \`npm install -g t3@${targetVersion}\`, or pick a version from the preview channel.`,
295
316
});
296
317
}
297
-
if(targetVersion===currentVersion){
298
-
yield*Console.log(`t3 is already on ${currentVersion} (${targetChannel}).`);
318
+
if(targetVersion===installedVersion){
319
+
yield*Console.log(
320
+
serviceVersion!==undefined
321
+
? `t3 and its background service are already on ${installedVersion} (${targetChannel}).`
322
+
: `t3 is already on ${installedVersion} (${targetChannel}).`,
` A server started by hand is still running ${currentVersion}at ${foreground.origin} (pid ${foreground.pid}). Stop it and start it again to pick up ${targetVersion}.`,
466
+
` A server started by hand is still running at ${foreground.origin} (pid ${foreground.pid}). Stop it and start it again to pick up ${targetVersion}.`,
0 commit comments