From e4c685e9bd549107023f3f3235549a3c6afd2a48 Mon Sep 17 00:00:00 2001 From: S'Bussiso Dube <80188685+Sbussiso@users.noreply.github.com> Date: Thu, 10 Sep 2026 15:27:01 -0700 Subject: [PATCH] Track CameraNode 0.1.77 in the cold-boot version floor MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit CameraNode released 0.1.77 — the first build whose assets carry the cameranode name. This constant is the disaster fallback for the latest-version lookup: the runtime normally resolves it dynamically from GitHub /releases/latest via app.core.release_cache, so it is read only on cold boot before the first refresh tick, and during a sustained GitHub outage. Bumped anyway, because the failure mode is silent and has happened before: this default sat at 0.1.26 while releases reached 0.1.73, so a cold boot mis-reported every node >= 0.1.26 as up to date. The comment beside it asks for exactly this. The LATEST_NODE_VERSION Fly secret is staged to 0.1.77 alongside, since the secret overrides this default in production and is the value that actually decides `update_available` there. Co-Authored-By: Claude Opus 5 --- backend/app/core/config.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/backend/app/core/config.py b/backend/app/core/config.py index f0c4623..20fbc7a 100644 --- a/backend/app/core/config.py +++ b/backend/app/core/config.py @@ -146,7 +146,7 @@ class Config: # drifts). It went stale at 0.1.26 while releases reached 0.1.73, # which on a cold boot mis-reported every node >=0.1.26 as current. MIN_SUPPORTED_NODE_VERSION: str = os.getenv("MIN_SUPPORTED_NODE_VERSION", "0.1.0") - LATEST_NODE_VERSION: str = os.getenv("LATEST_NODE_VERSION", "0.1.76") + LATEST_NODE_VERSION: str = os.getenv("LATEST_NODE_VERSION", "0.1.77") # ── API schema exposure ────────────────────────────────────────── # FastAPI's /api-docs, /api-redoc and /api/openapi.json were served