-
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
asdf latest
command should defer to plugin to determine latest version
#763
Comments
Will this also resolve #648 ? |
I have the same issue here. I am working on a plugin for age and even if age is stable enough for being recommended to use with sops among other use cases, the command Edit: After looking into it, the feature seems straightforward. If none is able to pick it up, I volunteer to try to implement it. |
This would fix the issue stated at asdf-vm/asdf#763
If the command `latest-stable` exists in the plugin, `asdf latest` defers to it to determine the latest stable version. Fixes asdf-vm#763
Is your feature request related to a problem? Please describe.
The
asdf latest
command assumes versions listed by thelist-all
command are semantic versions. This assumption is not necessarily correct for all plugins and could cause problems.Describe the solution you'd like
The
asdf latest
should invoke a plugin callback namedlatest-stable
when one is present to compute the latest version. If thelatest-stable
script is missing theasdf latest
command should fallback to computing the latest version as it does now by assuming the versions are semantic versions.Describe workarounds you've considered
None. This seems to be the most straightforward solution to this problem.
Additional context
This is actually what was requested for #216 but was never properly implemented.
The text was updated successfully, but these errors were encountered: