-
Notifications
You must be signed in to change notification settings - Fork 12
[FR] Show more than one version update type if available #75
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
Comments
Hi @ruudschilders! I'm not sure how easy it would be to implement this, but I'll take a look. In the meantime I could add a config option to ignore certain update types. Does that sound good? |
Yes that would help :-) |
I am interested in this feature as well, although in my case I would like to disable the checking of the latest tag and only show updates if the digest changes for the exact same tag (for e.g., My motivation is that these exact versions are the ones officially verified to work with the services I am running, and I don't want any updates to inadvertently break anything (and accept that this may lead to tradeoffs in security/bugfixes). I see that you already have a notion of
|
@ruudschilders v3.3.0 added an option to ignore certain update types. Check out the docs here! If it's enough for you, I'll close this issue, otherwise I'll keep it open and try to implement your original request. |
Yes, thank you! It can be closed |
Is your feature request related to a problem? Please describe.
I run certain images with a pinned version, for example postgres:15
cup now tells me there's a major upgrade available (postgres 17).
Describe the solution you'd like
I would like to be able to see if there are updates to the postgres:15 image (for example postgres:15.10 -> postgres 15.12) instead of being notified there's a major/minor upgrade when I have pinned the version.
Or better: I would like to be notified of both.
Additional context
Of course this wouldn't apply if you use :latest or even without version.
The text was updated successfully, but these errors were encountered: