Skip to content

Update status (admin)

HTTP routes and behavior for update status (admin).

GET /api/admin/update-status # latest-release comparison + management-portal URL
PUT /api/admin/update-status # set the management-portal URL ({ management_url })

Reports how the running build compares against the latest published GitHub release (windoze95/cantinarr), cached ~12h, best-effort and non-blocking; only builds stamped with a semver-parseable version check; stable and candidate images, plus edge/preview images built after the first release tag (their git describe stamp parses to the nearest release, so they compare on release cadence, never per merge). Dev and pre-first-tag builds never contact GitHub, and CANTINARR_DISABLE_UPDATE_CHECK=1 turns the check off. The app does not currently render this comparison anywhere: the app-wide “a newer Cantinarr is available” banner is off, so the endpoint is the only place the result surfaces. management_url is an optional admin-set link to a container-management portal, offered as the primary action of the “update the server” skew warning below. Unlike instance URLs (which only the server dials), this link opens on the admin’s own devices, so it must be reachable from them: a cluster-internal name that only the server resolves won’t work from a phone. The running version is also surfaced to all clients (for the About screen) in /api/config as version, alongside min_app_version: the oldest app build the server still fully supports (a constant in internal/version, "0.0.0" = no floor). An app below that floor shows a warn-only “update this app” banner; the app carries a matching minServerVersion floor for the reverse direction. Floors only move alongside a breaking change, and violations warn: they never block.

View the maintained source for this page.