You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the latest version in the helm action causes this code: https://github.com/Azure/setup-helm/blob/main/src/run.ts#L52 to attempt to lookup the latest release from the helm/helm github repo via the github graphql api. This api call limits the result set to 100, so once helm added more than 100 total releases, this fails to find the actual latest version. Currently it finds 1.2.1 which is quite an old helm version. (see api call log below)
This should be updated to correctly find the latest version by sorting the list via semver versioning rules using the entire result set (by pagination or using a larger than 100 number), OR better yet it should install the latest version using the script provided by the helm team listed in the docs here: https://helm.sh/docs/intro/install/
Version
I am using the latest version
Runner
self-hosted
Relevant log output
response from the api shows the latest version to be 1.2.1 according to the implementation here
This issue was created first but it is a duplicate of #99. There's more discussion on #99 so I'm going to close this for now.
it should install the latest version using the script provided by the helm team listed in the docs here: https://helm.sh/docs/intro/install/
We've looked into this install script before and opted not to use it because it doesn't work on Windows runners. Also this action needs to be able to support installing specific helm versions so we need some install functionality built into this action either way. If we could get it working for windows it does seem like a better solution.
What happened?
Using the latest version in the helm action causes this code: https://github.com/Azure/setup-helm/blob/main/src/run.ts#L52 to attempt to lookup the latest release from the helm/helm github repo via the github graphql api. This api call limits the result set to 100, so once helm added more than 100 total releases, this fails to find the actual latest version. Currently it finds
1.2.1
which is quite an old helm version. (see api call log below)This should be updated to correctly find the latest version by sorting the list via semver versioning rules using the entire result set (by pagination or using a larger than 100 number), OR better yet it should install the latest version using the script provided by the helm team listed in the docs here: https://helm.sh/docs/intro/install/
Version
Runner
self-hosted
Relevant log output
response from the api shows the latest version to be
1.2.1
according to the implementation hereThe text was updated successfully, but these errors were encountered: