phar-io/version

Issues

• ^7.3|^7.4|^8 Version string '8' does not follow SemVer semantics

  #36 opened 3 months ago by tacman
  1

• Branch version strings like dev-master are not supported

  #30 opened 6 months ago by llaville
  3

• greater than (e.g. >=3.6) not supported

  #34 opened 10 months ago by tacman
  3

• major version only not supported, e.g. ^6

  #35 opened 10 months ago by tacman
  1

• Warning during installation

  #14 opened 5 years ago by alextesi
  10

• VersionConstraintParser does not support logical OR represented by single pipe

  #28 opened 3 years ago by llaville
  6

• Make a new release

  #26 opened 4 years ago by addshore
  4

• Tilde operator without patch level

  #23 opened 4 years ago by seyon
  3

• [Regression] (in 3.0.1) Version::getVersionString will not return "v" prefix if used

  #24 opened 4 years ago by addshore
  3

• Exception marker interfaces shsould extend `Throwable`

  #16 opened 5 years ago by Ocramius
  2

• Warning during test, The attribute 'name' is required but missing.

  #18 opened 5 years ago by GuillaumeSeren
  1

• Ambiguous class resolution on composer dump-autoload

  #15 opened 5 years ago by winardiaris
  2

• Debian Version strings like 7.0.28-1 are not supported

  #10 opened 7 years ago by theseer
  4

• Version constraint ^3.0.0-alpha1 is not supported.

  #11 opened 6 years ago by sebastianheuer
  0

• Add support for 4.x and 4.* version constraints

  #9 opened 7 years ago by fabioneves
  2

• Add some usage examples to README.md

  #4 opened 8 years ago by dnaber-de
  1

• Make testing autoload building more obvious

  #6 opened 8 years ago by dnaber-de
  2

• Enforce valid version string in Version object

  #1 opened 8 years ago by sebastianbergmann
  0

• Add support for "^5.6 || ^7.0" as version constraint

  #2 opened 8 years ago by sebastianbergmann
  0