From 204d642e89c9fd8a57b341bb0c36849c88936eb0 Mon Sep 17 00:00:00 2001 From: Josh Poole Date: Thu, 13 Aug 2026 12:04:47 +0100 Subject: [PATCH] 20260813 - Bump config-merger pin to v0.4.3.0 The pin had been frozen at v0.3.17 since release v0.4.0, so every config-merger change since has been built and published by CI but never deployed. scripts/build_mender_artifact.sh sed-strips ${VAR:-default} down to the default literal, so the shipped artifact uses whatever this line says - and nothing sets CONFIG_MERGER_V. Two changes were stranded on every fielded node: - generate_retina_tracker_config (1936173) - wires retina-tracker's min_snr, so the GUI's Minimum SNR field has never reached the tracker; nodes silently run the image default or a stale retina-tracker.yaml instead - migrate_gain_reduction (e96c56d) - the scalar to per-tuner gainReduction migration Confirmed absent from the running v0.3.17 image on both Jonathan nodes. v0.4.3.0 is the newest published merger image and contains both. Symptom fix only: the pin is still a manual step that must be bumped every release. It should be derived from the release version instead, since the merger image is always published under that exact tag. Co-Authored-By: Claude Opus 5 --- docker-compose.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker-compose.yml b/docker-compose.yml index a105fff..bba3c19 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -17,7 +17,7 @@ services: config-merger: restart: "no" # Run once and exit - image: ghcr.io/offworldlabs/retina-config-merger:${CONFIG_MERGER_V:-v0.3.17} + image: ghcr.io/offworldlabs/retina-config-merger:${CONFIG_MERGER_V:-v0.4.3.0} volumes: - ${CONFIG_DIR:-/data/retina-node/config}:/data/retina-node/config - ${MENDER_COMPOSE_DIR:-/data/mender-docker-compose}:/data/mender-docker-compose