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 af1caa2
Browse filesBrowse the repository at this point in the historyBrowse files
fix(web): copy an update command that matches how the server is installed
The version-mismatch action hands every server that cannot update itself
`npx t3@<client-version>`. For a server installed globally with npm,
pnpm, or bun that command starts a second, throwaway copy instead of
updating the executable the user restarts, and for a server launched
through pnpm dlx or bunx it switches package runners.
The server now reports how its CLI is installed in a new
capabilities.serverInstall field, judged by where the resolved entry
script lives: a package runner's cache (npx, pnpm dlx, bunx) or a
package manager's global layout (npm, pnpm, bun). Project-local
installs, repo checkouts, and the pinned service runtime report
nothing. The field is only sent when serverSelfUpdate is absent, since
those are the only servers that hand out a command, and clients decode
unknown kinds as absent so a newer server cannot break an older client.
Clients pick the command from that kind: a global install gets its
package manager's upgrade command, a package runner is re-run at the
target version, and servers that report nothing keep the npx relaunch.
The user guide describes the command per install and keeps the explicit
instruction to stop the running server first.
0 commit comments