Repository navigation
20261024 - Bump image pins for v0.4.8.0 - #51
Merged
Merged
Conversation
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) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves the stack's image pins for the
v0.4.8.0release.RETINA_TRACKER_Vv0.5.0v0.6.0CONFIG_MERGER_Vv0.4.8.0-devv0.4.8.0Everything else stays where it is:
BLAH2_Vv0.7.0,SPECTRUM_Vv0.1.2,TELEMETRY_Vv0.5.0,TAR1090_Vv0.3.0,ADSB2DD_Vv0.1.3. None of thoserepos has a commit since the tag it is pinned to.
retina-tracker v0.6.0
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.
RETINA_TRACKER_Vis referenced twice, once for the tracker image and once inretina-telemetry's heartbeat, which reports which tracker produced the tracks
it is sending. The comment there already required the two defaults to agree, so
both move together.
CONFIG_MERGER_V
Set to the tag being cut, as every release does: config-merger is built from
this repo by this repo's own release workflow, which publishes it before the
Mender artifact is built, so referencing a tag that does not exist yet at commit
time is correct.
Worth calling out that the dev release left it at
v0.4.8.0-dev. Without thisbump the stable artifact would have shipped a dev merger image.
Header comment
The release comment at the top of
docker-compose.ymlnamed five of the sevenpins, leaving out
SPECTRUM_VandTELEMETRY_V, and said nothing about whyCONFIG_MERGER_Vis set to a tag that does not exist yet. It now names allseven, flags the duplicated tracker pin, and records that a stale
CONFIG_MERGER_Vsilently strands merger fixes, which is what happened for sixconsecutive releases.
Verification
Resolved the compose file exactly the way
scripts/build_mender_artifact.shdoes, and confirmed all ten image lines come out as literal tags, with none of
the
${VAR:-default}forms its guard rejects:docker compose configstill parses the file. The retina-trackerv0.6.0imageis confirmed published before this is tagged, since the artifact build pulls it
with skopeo.
Not verified: the artifact build itself, which runs on the release tag.
Docs
This repo has no
docs/directory. The header comment indocker-compose.ymlis the only documentation of the pins and is updated here.
STANDALONE.md's.envsamples name a few of these variables, but as illustrations of theoverride syntax rather than a record of current pins, so this change does not
make them wrong.
🤖 Generated with Claude Code