-
-
Notifications
You must be signed in to change notification settings - Fork 98
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
Error resolving pre-release version #184
Comments
What's the right way to define pre-release versions in shards? From https://semver.org:
|
Sorry, that's probably not supported. |
Fixing the detection of release tags, is easy (a mere regular expression), but then the pre-releases, which are unstable, would become the latest release for shards, which must be changed to distinguish stable releases from unstable pre-releases, default to releases, but still allow installing specified pre-releases, and probably add some command line argument to enable pre-releases by default... I.e. a lot of work. You may use |
I'm willing to work on this. I think a good solution would be to introduce a |
Why not attempt to parse the versions using the stdlib's semver parser and handle them properly instead of using regexes? |
Because We should have a generic Btw. |
It doesn't have to be complex. We can evolve SPEC to accept pre-releases as On the implementation side, we must first accept pre-releases:
Then modify
Maybe even:
|
Implementation is of course debatable, but I don't think that a specific version type would be overly complex. It would combine several aspects of handling versions in one place. More important at first is the design decision. This includes updating the specification which doesn't look completely right. |
TBH I don't care much. Following rubygems is probably simpler, which means accepting both |
I'm trying to use meta versions as described in SemVer. My lib has
v0.2.0-pre1
tag.My app's shard looks like this:
Getting
Error resolving mylib (0.2.0-pre1)
. What's wrong?The text was updated successfully, but these errors were encountered: