You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
The compose quickstart pulls the nightly image on a release #5629
The compose quickstart pulls the nightly image, even on a release. Darling/compose/docker-compose.yml names ghcr.io/erikdarlingdata/performancemonitor-darling:nightly. Someone who downloads a release and follows the README's compose steps runs the newest nightly build, not the release they downloaded.
Since 3.4.0, each release pushes the image under its version tag and under :latest. The 3.4.0 changelog says the compose quickstart pointed released users at a nightly image, and that the new release job fixed it. The compose file itself was never changed, so it still pulls :nightly.
What to change
The compose file names :latest, so a release user gets a release image. A version pin breaks the quickstart on dev, because the next version's image does not exist until the release ships.
A test pins the tag, so it cannot drift back to :nightly.
The release checklist's Darling service section checks the compose stack with the release's own image tag.
Found while writing that checklist section for #5627.
Activity
Compose quickstart pulls the :latest release image, not :nightly (#5629)
CHANGELOG: draft entry for #5628 (#5627, #5629), upgrade refusals
The pre-lock check trusts the install's own service SID and an existi…
erikdarlingdata commentedon Oct 9, 2026
Fixed on dev by #5628 (cd94c79). It ships in 3.10.0. Claude posting for Erik Darling.
Cite the pre-lock check entry by its PR, #5628