Request: Support building Helm v3 patch versions alongside v4

[nag-Soliton]

Hi, thank you for maintaining this repository!

I was looking at the build logs and noticed that the current workflow seems to only fetch and build the "latest" release from the Helm repository (https://api.github.com/repos/helm/helm/releases).

Problem:
Helm is currently transitioning from version 3 to version 4. My concern is that once Helm v4 is released and becomes the "latest" release on GitHub, the current build logic might stop picking up new patch releases for the v3 series (e.g., v3.19.x).

Evidence:
Looking at a recent build log (linked below), it appears the script specifically targets the single latest version:
[Link to the build log you provided: https://github.com/alpine-docker/helm/actions/runs/20738830288/job/59541475434]

Request:
Could you please update the CI/build logic to track and build the latest versions for both the v3 and v4 streams? Many users will likely remain on v3 for a while, so continuing to publish Docker images for v3 patch updates would be greatly appreciated.

Thanks in consideration!

[ozbillwang]

why not raise a PR for this request? Take reference on code at

https://github.com/alpine-docker/helm/blob/master/.github/workflows/build.yml#L33-L47

at a new session and the version to latest 3.