Improve wasmer run semver versions
Opened this issue · 3 comments
syrusakbary commented
Right now running
$ wasmer run pancake/r2@5.4.1
Fetches pancake/r2@5.9.0
(!!)
Feches a different version than wasmer run pancake/r2@=5.4.1
. Intiuitevely, we should use by default =
version, not "similar to"
syrusakbary commented
@ayys this may be a backend issue
theduke commented
This is most likely the dependency resolution code in the wasix
crate, not the backend.
I agree that in the CLI the semver logic is unintuitive.
In other contexts resolution should use semver, not an exact version, or potentially the exact version for theh root package, and semver otherwise.
This needs to be tweaked carefully to avoid breaking downstream logic.