Pin down Helm version in specific action version #97
Description
Helm version 3.18.0 introduced major issue with template generation see:
- typeIs/typeOf behavior has changed since helm 3.18.0 helm/helm#30880
- Possibly found a major bug in the new 3.18.0 version helm/helm#30878
Because this action installs latest helm available anyone that uses it can be affected (as myself). I think it would be better practice to pin down helm version with $DESIRED_VERSION (from get-helm.sh) and connect them with action releases so users can choose to use some helm version. Or even better, introduce ability to setup helm version for user in inputs with default latest (environmental variable unset).