Using volta-cli/action on GitHub Enterprise Server causes frequent rate-limits with no fallback

[ZauberNerd]

We are using this action on GitHub Enterprise Server and we're seeing frequent failures trying to get the latest volta-cli version, because we're not authenticated against GitHub.com.

For now we have pinned the volta-version to 1.0.8, but we would like to remove that pinning again, so that we will get the latest volta-cli version in the future.

I saw that the actions/setup-node action has a fallback to get the version directly from nodejs.org in case of rate-limits: https://github.com/actions/setup-node/blob/9f3a02bbd17adc05b078145bb8f676c84be77e89/src/installer.ts#L109-L129
Maybe something like that would make sense to implement in this action also.

I actually have two ideas that could solve this:

1. check if the request got rate-limited and fall back to https://volta.sh/latest-version
2. check if the request got rate-limited and do a HEAD request to https://github.com/volta-cli/volta/releases/latest which will redirect to the latest version

If there's interest and a suggestion on which route to take, I'd be willing to create a PR for it.

Ref: #77, #101, #97

[rwjblue]

Eeck, sorry about this. The changes in #101 were about moving away from using https://volta.sh/latest-version due to issues with the same sort of rate limiting failures that you are seeing now after #101.

check if the request got rate-limited and fall back to https://volta.sh/latest-version

I'd gladly accept a PR that adds this, if you have the time.