-
Notifications
You must be signed in to change notification settings - Fork 20
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
cargo install wadm - the '--version' provided, 'v0.4.0-alpha.1', is not a valid semver version
#97
Comments
Also noticed that crate failed to publish in worflow run here: Not sure how that wadm version is being installed haha, I don't find crate: https://crates.io/search?q=wadm -> Didn't notice git flag haha |
Tried to reproduce on an Ubuntu-22-04 VM via parallels, but same issue. Btw, uninstalling wadm (after installing it without specifying the version) implies that it indeed doesn't like the
|
the
--version provided,
v0.4.0-alpha.1, is not a valid semver version
the \
--version\ provided, \
v0.4.0-alpha.1\, is not a valid semver version
the \
--version\ provided, \
v0.4.0-alpha.1\, is not a valid semver version
the
--version provided,
v0.4.0-alpha.1, is not a valid semver version
were you able to drop the |
the
--version provided,
v0.4.0-alpha.1, is not a valid semver version
the '--version' provided, 'v0.4.0-alpha.1', is not a valid semver version
I didn't have to:
|
I need to read full messages lmao. I skim too much |
Cargo uses semver for versioning, with a major.minor.patch-pre format: major: Incompatible API changes So dk why alpha doesn't work, maybe it is the |
As far as I can tell from the semver spec dots are entirely allowed in prerelease identifiers |
We're updating install instructions though to just download the binary, so this shouldn't be a problem |
Definitely fixed by updating the README, but in case you want to do it, this works! cargo install wadm --version 0.4.0-alpha.2 |
Heyho,
super excited to see wadm taking shape, so I tried to follow install instructions on my M2. Unfortunately there seems to be an issue with semver detection of cargo for
v0.4.0-alpha.1
.Trying to run the command from the readme:
For now I was able to work around it via leaving out the
--version
flag.Thank you and keep up the great work!
The text was updated successfully, but these errors were encountered: