-
Notifications
You must be signed in to change notification settings - Fork 780
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
Support using "latest" version of a program (asdf {global,local,shell} <plugin> latest
)
#801
Comments
Currently
Examples of potential problems with this feature:
I'm sure there are more scenarios like this. Requiring specific versions, while strict, removes a class of issues and is the intended goal of |
That's what I meant with "Ideally the version ending up in |
Sorry, I didn't understand that to be what you meant. If it worked that way, then it doesn't have any issues I can think of off the top of my head 👍 |
I would also be fine with doing For example: $ asdf latest ruby
ruby 2.7.1
$ asdf local ruby latest
|
That's what the PR #802 is doing. 😊 |
asdf
kind of knows what versionlatest
is describing and allows installing the latest version of a program withasdf install <plugin> latest
, but setting the latest version of a program in the shell, in a directory, or globally requires specifying the exact version.Example:
Describe the solution you'd like
It would be great if
asdf {global,local,shell} <plugin> <version>
supportedlatest
as version.Ideally the version ending up in
.tool-versions
would be the resolved latest version of the program, e. g.jbang 0.45.0
in the example above.asdf
already supports this withasdf latest <plugin>
.The text was updated successfully, but these errors were encountered: