From d2816d8bb8467beafbb1b664dc02ba99c53b418b Mon Sep 17 00:00:00 2001 From: Josh Poole Date: Sat, 24 Oct 2026 12:29:00 +0100 Subject: [PATCH] 20261024 - Bump image pins for v0.4.8.0 retina-tracker moves to v0.6.0, which builds the node's coverage wedge from ADS-B-verified detections, marks where that wedge meets the processed range, serves the close-in slices apart from the main lobes, and no longer crashes or loses a reset on a damaged or contended wedge file. retina-gui v0.13.0 draws it, and ships in the matching owl-os release. The variable is referenced twice, once for the tracker image and once in retina-telemetry's heartbeat, which reports the tracker that produced the tracks it is sending. The comment there already said the two defaults have to agree, so both move together. CONFIG_MERGER_V goes to v0.4.8.0, matching the tag being cut, as it does every release. Note it was left at v0.4.8.0-dev by the dev release, so without this the stable artifact would have shipped a dev merger image. The header comment listed five of the seven pins, leaving out SPECTRUM_V and TELEMETRY_V, and said nothing about why CONFIG_MERGER_V is set to a tag that does not exist yet. It now names all seven, flags the duplicated tracker pin, and records that a stale CONFIG_MERGER_V silently strands merger fixes, which is what happened for six consecutive releases. That comment is the only documentation of the pins in this repo, so it is the place for it. Verified by resolving the compose file the way scripts/build_mender_artifact.sh does and confirming all ten image lines come out as literal tags, with none of the ${VAR:-default} forms its guard rejects, and that docker compose config still parses the file. Co-Authored-By: Claude Opus 5 (1M context) --- docker-compose.yml | 23 ++++++++++++++++++----- 1 file changed, 18 insertions(+), 5 deletions(-) diff --git a/docker-compose.yml b/docker-compose.yml index 0e9f919..c59be19 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -6,8 +6,21 @@ # # See .env.example for standalone configuration. # -# Releases: Update the version after :- in each image tag (e.g., :-v0.3.0 → :-v0.4.0) -# BLAH2_V, TAR1090_V, ADSB2DD_V, CONFIG_MERGER_V, RETINA_TRACKER_V +# Releases: Update the version after :- in each image tag (e.g., :-v0.3.0 → :-v0.4.0). +# All seven, so that none is silently left behind: +# BLAH2_V, SPECTRUM_V, RETINA_TRACKER_V, TELEMETRY_V, TAR1090_V, ADSB2DD_V, +# CONFIG_MERGER_V +# +# RETINA_TRACKER_V is referenced twice, once for the tracker image and once in +# retina-telemetry's heartbeat, and the two defaults have to agree. +# +# CONFIG_MERGER_V is not like the others. config-merger is built from this repo, +# by this repo's own release workflow, which publishes it before the Mender +# artifact is built. So it is always set to the retina-node version being +# tagged, even though that tag does not exist yet at commit time, and whether or +# not config-merger itself changed. Left at an older value it pins an image +# nothing rebuilds against, and merger fixes never reach a node: that happened +# for six consecutive releases. networks: blah2: @@ -17,7 +30,7 @@ services: config-merger: restart: "no" # Run once and exit - image: ghcr.io/offworldlabs/retina-config-merger:${CONFIG_MERGER_V:-v0.4.8.0-dev} + image: ghcr.io/offworldlabs/retina-config-merger:${CONFIG_MERGER_V:-v0.4.8.0} volumes: - ${CONFIG_DIR:-/data/retina-node/config}:/data/retina-node/config - ${MENDER_COMPOSE_DIR:-/data/mender-docker-compose}:/data/mender-docker-compose @@ -175,7 +188,7 @@ services: retina-tracker: restart: always - image: ghcr.io/offworldlabs/retina-tracker:${RETINA_TRACKER_V:-v0.5.0} + image: ghcr.io/offworldlabs/retina-tracker:${RETINA_TRACKER_V:-v0.6.0} network_mode: host depends_on: config-merger: @@ -267,6 +280,6 @@ services: # The same variable, and the same default, that pins retina-tracker's # image above: the frames carry that tracker's tracks since node ingest # 1.6.0, and the heartbeat names the release that produced them. - - RETINA_TRACKER_V=${RETINA_TRACKER_V:-v0.5.0} + - RETINA_TRACKER_V=${RETINA_TRACKER_V:-v0.6.0} - LOG_LEVEL=${TELEMETRY_LOG_LEVEL:-INFO} container_name: retina-telemetry