Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug: Latest version is grabbing alpha version of tool #97

Closed
1 task done
KenBurk opened this issue Oct 24, 2022 · 5 comments
Closed
1 task done

Bug: Latest version is grabbing alpha version of tool #97

KenBurk opened this issue Oct 24, 2022 · 5 comments
Labels
bug Something is not working

Comments

@KenBurk
Copy link

KenBurk commented Oct 24, 2022

What happened?

Expecting:
Helm tool version: 'v3.8.2' has been cached at /opt/hostedtoolcache/helm/3.8.2/x64/linux-amd64/helm
actual
Helm tool version: 'v3.0.0-alpha.1' has been cached at /opt/hostedtoolcache/helm/3.0.0-alpha.1/x64/linux-amd64/helm

Version

  • I am using the latest version

Runner

self-hosted

Relevant log output

Run azure/setup-helm@v1
with:
version: latest
...
creating: linux-amd64/
inflating: linux-amd64/helm
inflating: linux-amd64/LICENSE
inflating: linux-amd64/README.md

@KenBurk KenBurk added the bug Something is not working label Oct 24, 2022
@kxiao-msk
Copy link

we face the same issue, can this be fixed ASAP?

@ShiroTian
Copy link

me too

@umutkacar
Copy link

umutkacar commented Oct 25, 2022

We were using azure/setup-helm@18bc76811624f360dbd7f18c2d4ecb32c7b87bab # v1 and we also encountered this issue.

It was installing an alpha version: Helm tool version: 'v3.0.0-alpha.1' has been cached at /opt/hostedtoolcache/helm/3.0.0-alpha.1/x64/linux-amd64/helm and it was complaining at the deploy step by throwing: Error: unknown flag: --atomic

Switching to azure/setup-helm@20d2b4f98d41febe2bbca46408499dbb535b6258 # v3.0 seems to have fixed the issue.

I need to observe a little more to confirm.

@OliverMKing
Copy link
Collaborator

This will be fixed in #100. I'm going to roll it out as soon as possible. #98 and #99 are duplicates of this.

@OliverMKing
Copy link
Collaborator

This has been fixed and released in v3.4 (and v3). Please upgrade to one of these versions. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

No branches or pull requests

5 participants