Terraform-provider-helm: Publish GitHub releases during provider releases

[pdecat]

Releases are published by updating the changelog, pushing a binary, and making a GitHub "tag" release.
Users can't subscribe to these releases automatically, though: https://github.community/t5/How-to-use-Git-and-GitHub/Not-getting-release-notification-despite-quot-Watching-releases/td-p/19665.

It would be awesome to publish rich releases on GitHub, allowing users to subscribe.

Both the Azure and AWS providers do this already.

Note: it used to be done until release 0.6.0 of the helm provider which currently appears as the latest one despite several tagged releases:

[rporres]

cc @alexsomesan This is something that should be standardised from a Hashicorp perspective

[alexsomesan]

I agree. This is something we're considering and have started discussing to come to a common standard.

[marcelloromani]

Pardon my peskyness, but I don't see the need to wait for a global decision on whether to use GH releases or not to start using them again, considering:

• AWS and Azure are (still) using them, as mentioned
• They were used up to 0.6.0, and it's not clear why this has stopped
• Using GH releases clearly provides a much better user experience than tags alone

[rporres]

They were used up to 0.6.0, and it's not clear why this has stopped

That happened when repository was transferred from the original developer's github account to the official terraform-providers organization. At that moment the common practise was adopted but the old releases were not removed, hence the confusion

[marcelloromani]

Thanks @rporres for the explanation.

[pdecat]

Current work-around: subscribe to https://github.com/terraform-providers/terraform-provider-helm/tags.atom with a feed reader

[pdecat]

it used to be done until release 0.6.0 of the helm provider which currently appears as the latest one despite several tagged releases

What about deleting the old releases to eliminate the confusion until a long term solution is implemented?

[marcelloromani]

@pdecat Very much against it, as that would suddenly break things for the poor souls still deploying 0.6.0 :-)

[rporres]

@marcelloromani I fail to see how people will deploy 0.6.0 if it's not manually as it is not in the official release page https://releases.hashicorp.com/terraform-provider-helm/. 0.6.1 is actually the same thing as 0.6.0 but released as the official provider

I agree with @pdecat that current situation is the worse of the two worlds, so I'd prefer to delete old releases (which do not correspond to anything officially released by hashicorp) to avoid confusion, but we need @alexsomesan input here

[pdecat]

Hi, I just meant deleting the Github releases, not the tags, nor the artifacts available at https://releases.hashicorp.com/terraform-provider-helm/

[pdecat]

Oh, I did not notice 0.6.0 and older release artifacts were not available at https://releases.hashicorp.com/terraform-provider-helm/

[rporres]

I'm not sure if they can be uploaded or not as it will need to be a manual process and that belongs to Hashicorp internals :)

[marcelloromani]

Surely putting a note pointing to https://releases.hashicorp.com/terraform-provider-helm/ won't hurt?

[pdecat]

Github releases are now published during the release process since v0.10.3 :tada:

https://github.com/terraform-providers/terraform-provider-helm/releases