Update notifications

Update checks are opt-in: set JANUS_UPDATE_CHECK=true in the gateway environment. They are disabled by default and hard-disabled by JANUS_OFFLINE=true. The local evaluation launcher clears ambient JANUS_* settings and does not enable checks.

When enabled, the gateway periodically requests:

GET https://janusedge.com/api/v1/updates/check?version=<current>&edition=<edition>&channel=stable

The request includes the gateway's instance identifier in X-Janus-Instance, independently of license sync. It does not include prompts, responses, user identities, or model traffic. As with any HTTP request, the service also receives the source IP address.

The catalog is filled from GitHub Releases by janusedge.com itself: every ten minutes it polls the repository, downloads each new release's assets, verifies them against SHA256SUMS, and records the container image digest. A release becomes public — on this site, in the changelog, and in update-check responses — only after that verification and an administrator's approval; a yanked release disappears from all three at once.

The response describes the latest published catalog entry (latest, published, notes_url, advisory, min_supported, image_digest, update_available, and unsupported). An empty release catalog returns latest: null and update_available: false; this does not prove there are no GitHub releases. Check the public releases directly if the catalog is unavailable or empty.

Check the result in Admin → System → License. Notifications do not download or install upgrades. Read the upgrade and backup guide before changing versions.