Appearance
ts version
Print the version of the ts executable you are running. Reach for it when a command behaves differently than the documentation describes and you need to know which build is on the machine.
Usage
text
ts versionDescription
ts version reports the CLI's own version, in all four fields, and its build: the version plus the commit a CI build stamps after it. Builds of one day differ only in the fourth field. It does not contact a server, so it works signed out, offline, and before any server has been configured.
The server's version is a separate thing, and this command will not tell you what it is — --server and --local are accepted, because every command accepts them, but they change nothing here. The two can legitimately differ: administrator workstations often run a newer ts than the servers they manage.
With --format=json the version and build also appear as version and build fields in the result envelope, which is the reliable way to gate a script on the CLI being new enough for a command.
Examples
bash
# Which ts is on this machine?
ts version
# For a script that needs to check the build
ts version --format=jsonbash
# This reports the CLI on your workstation, not the server's version
ts --server=https://turbo.example.net versionOutput
text
Turbo Server CLI version 1.0.0.0
Build 1.0.0.0+4b8e2f1c9aWith --format=json:
json
[{
"name": "version",
"arguments": ["version", "--format", "json"],
"result": { "exitCode": 0, "version": "1.0.0.0", "build": "1.0.0.0+4b8e2f1c9a" },
"messages": ["Turbo Server CLI version 1.0.0.0", "Build 1.0.0.0+4b8e2f1c9a"]
}]Exit Codes
0, always. Nothing is looked up and no server is contacted, so the connection, sign-in, and not-found codes cannot occur.
