Bump version if another dependency changed #29146
Replies: 3 comments
-
Not sure if this is your usecase, but adding
In the example above |
Beta Was this translation helpful? Give feedback.
-
And there is a working workaround including running a script in a postUpgradeAction to change things. |
Beta Was this translation helpful? Give feedback.
-
I think this open issue is what you want? Somebody attempted to get it working, with this PR: But we had to revert that soon after, because it was broken (not sure how/why it was broken). The revert PR is: That's why the issue is still open. |
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'm feeling kinda stupid at the moment... this is confusing me)
I have a repository with a directory containing helm-charts (v3). I managed to get updates working in
helm-values
, as well as using a RegexManager in the Chartfiles. To be able to release those, the Chart-versions need to be bumped as well. I'm aware this is a long story and that it's still not working by default.Question: Can I instruct renovate to bump an artificial version string depending on another version change? To be precise I want renovate to use one of the two methods mentioned above to recognize a (for example) minor update, to subsequently bump the artificial version in the
Chart.yaml
by one minor version.Any help is appreciated!
Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions