I have two environments each with two services, each deployed from Docker images published to GHCR. In my staging environment, the tag is set to main; in my production environment it is set to latest. Auto update is set to any time.

Three of these services work as expected (although the update detection interval is a bit slower than you’d really want for CD), but one (latest tag) constantly detects updates to the image and redeploys the same image. I have tried disconnecting from the image, with and without the latest tag, and the issue persists. I built the production environment by copying from the staging environment. I have not tried deleting and recreating the service. If I disable the auto-update functionality, the 'update available' notification persists.

I suspect the solution I go with will be hitting the CLI from GitHub Actions, due to the requirement to redeploy as soon as a build has completed. But nonetheless I think this may be a bug in your auto update detection logic.

Many thanks!