Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use versioning combined with latest tag in wud.tag.include #503

Open
RK62 opened this issue Dec 4, 2024 · 3 comments
Open

Use versioning combined with latest tag in wud.tag.include #503

RK62 opened this issue Dec 4, 2024 · 3 comments

Comments

@RK62
Copy link

RK62 commented Dec 4, 2024

I would like to use versioning, but here only the latest labels.
For example see https://hub.docker.com/r/portainer/portainer-ce/tags:
currently 2.24.1 is the most recent version, but latest tag is 2.21.4

How can I realize this setting? The following configuration in Compose always gives me 2.24.1 as the latest version:

  --label ‘wud.tag.include=^\d+\.\d+\.\d+$’ \
  --label ‘wud.link.template=https://github.com/portainer/portainer/releases/tag/${major}.${minor}.${patch}’ \
  --label ‘wud.display.icon=si:portainer’ \

I don't want to use wud.watch.digest=true because then I lose the versions and the link to the changes.
Is it possible to select the latest tag get the assigned version?

@fmartinou
Copy link
Collaborator

Hi,

Sorry, there is no way to achieve that.

The portainer situation is weird.
If I understand well, the most recent versions are 2.24.x but 2.21.x are the latest LTS versions so portainer tag them as latest ?
That's pretty uncommon 🤔

@RK62
Copy link
Author

RK62 commented Dec 4, 2024

Yes, that is the situation on portainer.
OK, so know that I don't have to search and test any longer and have to observe this container manually.
Thanks for the quick reply and all the work, I really love WUD!

@tobidemski
Copy link

I probably have the same question / issue and also seeing this with n8n.
https://github.com/n8n-io/n8n/releases
They release different versions for example 1.72.1 which is also the "latest" but 1.73.1 is the most recent version.
Now I'm getting always a notification "Container n8n running with tag 1.72.1 can be updated to tag 1.73.1 on host 'local'"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants