Update Image Tag in Helm Values Specified By a Git Hash #28168
Replies: 2 comments
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. To get started, please read our guide on creating a minimal reproduction. Good luck, The Renovate team |
Beta Was this translation helpful? Give feedback.
-
When git hashes are used for a tag, and don't sort in any particular order, how could Renovate determine which one is latest? |
Beta Was this translation helpful? Give feedback.
-
What would you like help with?
I would like help with my configuration
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
No response
Please tell us more about your question or problem
I have a repository used by flux where I define Helm releases. In some of these I specify a specific image and tag.
When using Git hashes as tags (e.g. for an image hosted in GHCR), Renovate doesn't detect it and neither creates a PR for an update with a newer tag.
Example:
0f417aaec04572276755b6ab502dacec166a0ec3
was released 17 days ago. The current tagb5d25f5e4f8bafe8e0e58228006218af11182375
was released about a day ago.My Renovate config file is:
Renovate doesn't detect the newer image and, hence, no update PR is created.
Is it possible for Renovate to detect such tag updates?
Logs (not relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions