* fix: retry latest version lookup and add latest-fallback opt-out
Resolving 'version: latest' made a single request to
https://get.helm.sh/helm-latest-version and, on any failure, silently
installed the hard-coded default version. Since 'latest' resolves to
Helm 4, that fallback moves a job back a whole major version while the
step stays green.
Retry the lookup a few times with a short backoff, treat non-2xx
responses as failures instead of installing the response body, and add
a 'latest-fallback' input so callers can make the step fail instead of
installing the default version. The default keeps the existing
behavior.
* fix: do not fall back across a major version by default
Make 'latest-fallback' default to 'false', so an exhausted lookup fails
the step with the underlying error instead of installing the built-in
default version, which can be a major behind what 'latest' resolves to.
Setting the input to 'true' restores the previous behavior.
* fix: keep latest-fallback on by default
Installing the built-in default version when 'latest' cannot be
determined is documented behavior for v5, so 'latest-fallback' now
defaults to 'true' and callers opt out with 'false'. The warning
emitted on fallback names the input, so the downgrade is easy to trace
and to turn off.
* fix: cancel the unread body of a failed latest version response
A non-2xx response from the latest version URL is turned into an error
without reading its body. Cancel the body first, so its connection is
released before the next attempt instead of waiting for garbage
collection.
* Action update:
- Bump all dependencies
- Rewrite `getLatestHelmVersion()` function without graphql
* Bump stableHelmVersion
* Update readme and action.yaml
* Revert and rewrite with @octokit/action
* Add latest to integration test
* Bump action's versions
* Set github.token as default input
* Replace deprecated jest methods
* Add prettier to dev dependencies, fix prettier issues