Connector releases
What has changed, and how updates are delivered.
Current
v—
The first general release. Pairing, the request relay, health reporting, start-with-Windows, single-instance protection and a sign-in key locked to your Windows account.
How updates work
The connector updates itself: it checks for a newer build, verifies the download against its checksum, keeps your pairing and settings, and restarts. Nothing to reinstall. To check straight away, open ··· in the connector and choose Check for updates.
The manifest
Public, so a connector can poll it without credentials. Carries no customer data.
GET /api/v1/agent/manifest?version=1.0.0
{
"data": {
"currentVersion": "1.0.0",
"latestVersion": "1.0.0",
"updateAvailable": false,
"mandatory": false,
"downloadUrl": "…",
"sha256": "…",
"installPolicy": {
"preservesConfiguration": true,
"restartsAutomatically": true,
"verifiesChecksumBeforeInstall": true
}
}
}No checksum means no update
If a deployment has not published a checksum for its build, the manifest returns no download URL at all. Advertising an update that cannot be verified would be worse than advertising none.
Mandatory updates
A version below the stated minimum must update before it can connect. Reserved for protocol or security changes, and rare.
Something missing on this page? Tell us and we will fix it.