vdurmont/semver4j

Issues

• Missing patch number in one of the Semver breaks the comparison logic

  #70 opened 2 years ago by tejasjadhav
  1

• version compare error

  #72 opened 9 months ago by jzyjinziyan
  0

• add support for additional number after pre-release identifier

  #71 opened a year ago by RussiaVk
  0

• Semver does not follow Comparable contract for non standard versions

  #69 opened 2 years ago by anderruiz
  1

• Plans to handle any pull requests?

  #57 opened 4 years ago by theshoeshiner
  4

• NPE when using Requirement.buildNPM with ^16.0.0-0

  #63 opened 3 years ago by mealingr
  2

• Compare versions without patch level returns unexpected results

  #59 opened 3 years ago by npitch
  1

• Is this correct behaviour when comparing versions

  #15 opened 7 years ago by aslak-dirdal
  8

• Exception thrown for Requirement.buildNPM("1.0.0-setup-20220428123901")

  #66 opened 3 years ago by segovia
  1

• Ivy version range `[1.0,2.0]` is not satisfied by `1.0`

  #67 opened 3 years ago by MarcelBochtler
  1

• NPM compatibility

  #7 opened 8 years ago by algobardo
  5

• Invalid Suffix

  #40 opened 5 years ago by amiel92
  2

• Semver("1.0", NPM).satisfies("1.0") is false

  #51 opened 4 years ago by dac2k9
  1

• Inconsistent isSatisfiedBy for NPM mode and potential incorrect isEquivalentTo for NPM mode

  #46 opened 4 years ago by leaf94
  2

• Incorrect satisfies result for NPM type

  #29 opened 7 years ago by hsz
  2

• Issue with hyphen sign when used in build and pre release section

  #16 opened 7 years ago by KristianShishoev
  4

• Semver.isEquivalentTo() returns always false for larger major versions and SemverType.NPM

  #53 opened 4 years ago by oheger-bosch
  1

• NPM satisfies issue with optional version

  #48 opened 4 years ago by andrewvsk
  3

• isEqualTo has broken semantics for NPM type (is not symmetric)

  #43 opened 5 years ago by broglep-work
  2

• Compare version number with rc is incorrect

  #38 opened 5 years ago by shuyingz
  6

• Version 1.1.1.1 is considered as valid version

  #60 opened 3 years ago by obfischer
  3

• [Feature Request] Add SemverType.FREESTYLE

  #65 opened 3 years ago by johnny-the-coder
  0

• Add key to PGP keys map

  #62 opened 3 years ago by silnith
  0

• IncludePrerelease flag feature

  #58 opened 4 years ago by trish123
  0

• make validation method public

  #55 opened 4 years ago by sahilparikh98
  0

• Question: is this stable now?

  #44 opened 5 years ago by pdubb29
  1

• Incorrect satisfies result for NPM type

  #35 opened 5 years ago by morad3741
  1

• Add withSuffix (or addSuffix) and withBuild methods

  #30 opened 5 years ago by punkstarman
  2

• compareTo takes into account build number

  #26 opened 7 years ago by rupebac
  0

• Wrong comparison results when number of suffixes differ

  #27 opened 7 years ago by rupebac
  1

• Please create a new release with recent changes

  #24 opened 7 years ago by sschuberth
  2

• Semver.toString() adds additional information to the version string

  #5 opened 7 years ago by nictas
  5

• Issue with prerelease tags/npm

  #8 opened 8 years ago by tdraier
  1

• Matching a version against a composite range sometimes returns a wrong result

  #3 opened 8 years ago by nictas
  1

• Invalid operator priority

  #9 opened 8 years ago by tdraier
  2

• Ranges do not support versions with suffix tokens

  #2 opened 9 years ago by nictas
  1

• Empty string is not treated as `*` when used as a range

  #1 opened 9 years ago by nictas
  0