Renovate: Helm dependencies should optionally bump chart.yaml

[adusumillipraveen]

What would you like Renovate to be able to do?
It is great that renovate supports helm dependency management now. But, it would be great if renovate can optionally bump the chart version in chart.yaml in the PR as the new chart needs to be published as a new vesion.

Describe the solution you'd like
Renovate should (optionally ) bump the chart version in Chart.yaml when raising a PR to bump requirements.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Currently one way is to manually edit it so that we can publish a new version of chart.

Additional context
NA

[JamieMagee]

Yeah, this should be possible. We already have this functionality for bumping the version in package.json using the bumpVersion option, so extending this to work with helm shouldn't be too difficult.

[travisgroth]

Hi @rarkins I'd love to see this feature included. Can I help with the requirements or testing at all?

Functionality like https://docs.renovatebot.com/configuration-options/#bumpversion would be great.

To implement this, the version field in Chart.yaml needs the increment.

[rarkins]

@travisgroth which of our managers would this be applicable to? e.g. helmv3?

It will be a little bit tricky because npm's updating approach is quite unique compared to other managers and so therefore you can't simply copy over the way it does bumpVersion too.

I think we'd need to add an optional new function to managers with same or similar signature as this one in npm: https://github.com/renovatebot/renovate/blob/de5de8e097bd273b131f99eb68c61e121cfa9334/lib/manager/npm/update.ts#L7-L58

Then we'd need to work out where/how to call it, potentially here: https://github.com/renovatebot/renovate/blob/4665dbff6fe96c4aa2665d95022284c60be3f320/lib/workers/branch/get-updated.ts#L86

[travisgroth]

@travisgroth which of our managers would this be applicable to? e.g. helmv3?

My immediate use case is for helm-values, but I believe you'd want the option on any changes to a chart. So:

• helmv3
• helm-requirements
• helm-values

[mikebryant]

I've got an implementation of this going for helmv3 at #7670 :)