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

goenv doesn't respect versions set by aliases anymore #404

Open
pouneh opened this issue Oct 10, 2024 · 2 comments
Open

goenv doesn't respect versions set by aliases anymore #404

pouneh opened this issue Oct 10, 2024 · 2 comments

Comments

@pouneh
Copy link

pouneh commented Oct 10, 2024

Using a previous version of goenv, I was able to install go 1.21.13 aliased as 1.21. This results in a folder under $GOENV_ROOT/versions/1.21

In that prior version (I think I used 2.1.4), goenv version successfully used 1.21 as the version. Now, it can't find it and insists that the version is set to 1.21.13. Under the hood, yes it's 1.21.13, but now none of my shims work. I get the error message

goenv: 'package_name' command not found

The 'package_name' command exists in these Go versions:
1.21
@ChronosMasterOfAllTime
Copy link
Contributor

Ok thanks for bringing it up. We will look into it

@ChronosMasterOfAllTime
Copy link
Contributor

ChronosMasterOfAllTime commented Dec 19, 2024

This is a regression in behavior since 2.2.X after investigating. @reneleonhardt - think you can take this one

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

No branches or pull requests

2 participants