Docker image latest tag should point to latest release instead of main branch #1241

Closed
opened 2025-11-11 14:40:52 -06:00 by GiteaMirror · 0 comments
Owner

Originally created by @acidghost on GitHub (Jun 13, 2024).

Tools like diun can be used to watch for updates to Docker images.
The way it works is via container tags: deploy an image like image:tag and you'll get notified of new versions of that tag.

Usually by watching the latest tag you get updates for released versions. This is not the case for this project, the main and latest tags are the same.

ATM I could watch for a specific version, e.g. 0.3, and get updates for any 0.3.x, but I would not get updates for any 0.4.x.

IMO the latest tag should point to the latest release and the main and dev tags can point to the respective branches for people who want that.

Originally created by @acidghost on GitHub (Jun 13, 2024). Tools like [diun](https://github.com/crazy-max/diun) can be used to watch for updates to Docker images. The way it works is via container tags: deploy an image like `image:tag` and you'll get notified of new versions of that tag. Usually by watching the `latest` tag you get updates for _released_ versions. This is not the case for this project, the `main` and `latest` tags are the same. ATM I could watch for a specific version, e.g. `0.3`, and get updates for any `0.3.x`, but I would not get updates for any `0.4.x`. IMO the `latest` tag should point to the latest release and the `main` and `dev` tags can point to the respective branches for people who want that.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#1241