asdf latest command should defer to plugin to determine latest version
#763
Labels
Milestone
Comments
|
Will this also resolve #648 ? |
This was referenced Apr 27, 2021
|
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. |
threkk
added a commit
to threkk/asdf-age
that referenced
this issue
May 11, 2021
This would fix the issue stated at asdf-vm/asdf#763
threkk
added a commit
to threkk/asdf
that referenced
this issue
May 11, 2021
If the command `latest-stable` exists in the plugin, `asdf latest` defers to it to determine the latest stable version. Fixes asdf-vm#763
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
The
asdf latestcommand assumes versions listed by thelist-allcommand are semantic versions. This assumption is not necessarily correct for all plugins and could cause problems.Describe the solution you'd like
The
asdf latestshould invoke a plugin callback namedlatest-stablewhen one is present to compute the latest version. If thelatest-stablescript is missing theasdf latestcommand 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: