-
Notifications
You must be signed in to change notification settings - Fork 47
Issues: vdurmont/semver4j
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Missing patch number in one of the Semver breaks the comparison logic
#70
opened Mar 6, 2023 by
tejasjadhav
Semver does not follow Comparable contract for non standard versions
#69
opened Dec 1, 2022 by
anderruiz
Exception thrown for Requirement.buildNPM("1.0.0-setup-20220428123901")
#66
opened May 13, 2022 by
segovia
Semver.isEquivalentTo() returns always false for larger major versions and SemverType.NPM
#53
opened Mar 8, 2021 by
oheger-bosch
Inconsistent isSatisfiedBy for NPM mode and potential incorrect isEquivalentTo for NPM mode
#46
opened Sep 1, 2020 by
leaf94
isEqualTo has broken semantics for NPM type (is not symmetric)
#43
opened Jan 23, 2020 by
broglep-work
Issue with hyphen sign when used in build and pre release section
#16
opened Oct 16, 2017 by
KristianShishoev
ProTip!
Exclude everything labeled
bug
with -label:bug.