Instance health and version

These endpoints do not require a dashboard session or API token. They describe the running server, not an app release.

Method and path	Success	Response
GET /healthz	200	JSON health and build information
GET /api/v1/version	200	JSON current and latest ReleaseDesk release information

Health

curl "$RD_URL/healthz"

{"status":"ok","version":"0.9.0","commitHash":"abc123","uptimeSeconds":3600}

status is ok; uptimeSeconds is rounded seconds since this server process started. version and commitHash come from the server build metadata. A development checkout defaults to version: "dev" and an empty commit hash. The root package.json version is package metadata; inspect /healthz for the deployed server's version.

Available ReleaseDesk update

curl "$RD_URL/api/v1/version"

{"current":"0.9.0","latest":"0.9.1","updateAvailable":true,"releaseUrl":"https://github.com/SpacerunApp/releasedesk/releases/tag/v0.9.1","releaseNotes":"Release notes"}

current is the running server version. latest, releaseUrl, and releaseNotes describe the latest GitHub release; each is nullable. updateAvailable compares the numeric major, minor, and patch components when both versions can be parsed. The server caches the GitHub lookup for six hours and times it out after five seconds. RD_UPDATE_CHECK=false disables the lookup; it is also skipped for current: "dev". In those cases, or when GitHub cannot be reached, the latest-release fields are null and updateAvailable is false. A false value with latest: null does not confirm that the server is up to date.

For app build updates delivered to users, see Update feeds.