-
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
Feat/version compare #56
Conversation
While we are here shouldn't we rather start checking for version X.*, not >= X.0 ? Not only theoretically major semver version uptick may cause issues but as issue #6 shows it also happens in practice. |
I mean that I think that we should test if the major version is equal to expected, not equal or greater than. |
Got it. @ShimmerGlass what do you think? |
5b057bd
to
5caf2fa
Compare
I agree with @gdubicki, it's probably better to require a specific major version |
5caf2fa
to
03a8805
Compare
It makes sense to me too. Updated. |
…urrent program version Fixed regex used to extract program version. `version` arg was unused. Now, it is renamed as `minVer` and used in comparison. Additional `compareVersion` func added to compare minVer with currVer. Comparision with `strings.Compare` didn't worked for cases like `0.1.10 > 0.1.2` and therefore it is removed. Added unit test for `compareVersion` func.
03a8805
to
9d0c478
Compare
No description provided.