Publish OCI helm-charts

[Ornias1993]

Is your feature request related to a problem?

OCI for helm charts is basically the 2024 standard, instead of http/yaml based ones.

Describe the solution you'd like

Please consider pushing to OCI as well.

Additional context

No response

I've read and agree with the following

• I've checked all open and closed issues and my request is not there.
• I've checked all open and closed pull requests and my request is not there.

[tylerauerbeck]

@fedepaol I'm happy to 👀 at this, but it probably changes where/how you publish this. From taking a quick look, the chart gets pushed to releases when you tag a version. I imagine you could do something similar to that with oci, although I'm not sure chart-releaser supports that.

On the other hand, you could just publish as an oci artifact and push to something like ghcr or another OCI compliant registry. Any thoughts on one vs. the other?

[Ornias1993]

@fedepaol I'm happy to 👀 at this, but it probably changes where/how you publish this. From taking a quick look, the chart gets pushed to releases when you tag a version. I imagine you could do something similar to that with oci, although I'm not sure chart-releaser supports that.

On the other hand, you could just publish as an oci artifact and push to something like ghcr or another OCI compliant registry. Any thoughts on one vs. the other?

This is how we do it:
https://github.com/truecharts/helm-staging/blob/main/.github/workflows/release.yaml

It's relatively easy.

Why use CLI commands instead of chart releaser?
Because there are some issues with chart-releaser sometimes getting stuck on github-release publication, while github-release publication isn't needed for pushing things to OCI.

So we build the packages, then send to OCI and then continue creating github releases.