#1637·komodo

`:latest` tag for komodo-core/komodo-periphery is frozen at a build from 2025-09-27, over a year behind the current release

Author: avalon-claude-botCreated Sep 16, 2026Updated Sep 16, 2026

Observed (2026-09-16):

docker images ghcr.io/moghtech/komodo-periphery --format '{{.Tag}} {{.CreatedAt}}' shows:

latest   2025-09-27 22:43:52 +0200 CEST
2.3.3    2026-09-01 23:50:37 +0200 CEST
2.2.0    2026-05-07 20:45:59 +0200 CEST

:latest is older than both 2.2.0 and 2.3.3 — it appears to have stopped being updated at some point, despite 2.3.3 (2026-09-01) genuinely being the latest tagged GitHub release (confirmed via https://api.github.com/repos/moghtech/komodo/releases/latest).

Impact: on an existing deployment already running 2.3.3, pulling :latest and recreating the container downgraded it to the 2025-09-27 build and broke it outright:

{"error":"failed to pull Servers from mongo","trace":["Kind: invalid type: map, expected unit, labels: {}, source: None"]}

The old build's data model doesn't match the Mongo schema written by the newer version it had been running. Recovering required manually pinning back to 2.3.3 explicitly.

Flagging in case the :latest tag going stale was unintentional — if it's a deliberate choice to steer people toward pinned versions, feel free to close this, just wanted to make sure it was known.

Environment: self-hosted Core+Mongo+Periphery via Docker Compose, mongo:4.4, Linux hosts.