feat(helm/release-chart): update version for umbrella chart children

[neilime]

No description provided.

[neilime]

@fredleger it is complicated to upgrade the umbrella chart children versions.

Because if we change the version of a child, we must change the root Chart dependencies version so we must run helm dependency update (https://github.com/hoverkraft-tech/ci-github-container/actions/runs/10176351460/job/28145583710?pr=329#step:4:291)

It's not good to me because we don't have control on what we update.

What's your opinion?

[fredleger]

That's true I didn't anticipate this point. My bad.

About the control I'm not sure, if this is a real dependency like mysql the version is locked by the semver used.

If it's one of our child deps then we know what we are updating.

Maybe I'm missing something in the picture here. Let me know.

Another way maybe to find a way to do only partial updates of lock file but I'm not sure it's even possible.

[neilime]

• It seems impossible to update a specific dependency
• Relying on semver version is dangerous as it depends which kind of version is used (By example, Helm recommends the use of version ranges - https://helm.sh/docs/chart_best_practices/dependencies/#versions)
• The only way to me is to update the Chart.lock manually, but I dont know how (we need to reverse engineer helm) and I dont think it is a good solution

[fredleger]

I think limiting it to dependencies starting with file protocol is clever and give good control over it

[neilime]

I think limiting it to dependencies starting with file protocol is clever and give good control over it

How can we do it?

[neilime]

@fredleger should check it