semver

semver copied to clipboard

Add stable tag

3

Please tag the master branch so that composer configurations can be fixed to a certain commit.

iverberk

Version::next

1

Hey I saw there is a Version::next() in master but not in any of the tags.. i see it was merged quite some time ago.. Are there any plans for...

cdekok

Wrong sorting for patches

1

I was trying to use your module and... ``` 1.7.0-alpha.0 1.7.0-patch.0 1.7.0-patch2.0 1.7.0-patch.1 1.7.0-patch3.0 1.7.0-patch4.0 1.7.0 ``` Patch must be in the end as I understand.

andkirby

Hello, First of all, I want to congratulate your project. It'll be very useful. I'm using semver to manage versions of a library I'm implementing, and, I noticed a small...

glandre

The include didn't end up in the right spot

jenolan

also added a testcase to prevent this bug to happen again

schorsch3000

You may benefit from using `@DataProvider` for your tests. I believe it would save you lots of lines of code and allow you to make new scenarios by just adding...

jonmchan

Sorting with build versions: Normal version should be larger than build version

5

Hi again. Semver 2.0.0 states in bullet point 11 that "Build metadata does not figure into precedence". Furthermore it states that "Build metadata SHOULD be ignored when determining version precedence."...

binwiederhier

detect and remove leading 'v' and pad missing version components

3

the library should look for a leading 'v' ex. 'v.1.2.3' and remove it (since it's not part of the standard) also pading 0 for missing version parts ex. (1.3 becomes...

burn2delete

Include dashes in build meadata, e.g. 0.1.0+SNAPSHOT-123.git456

1

Hi, thanks for the library. In bullet point 10, semver 2.0.0 states about build metadata: "Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]." You library currently complains that "0.1.0+SNAPSHOT-123.git456"...

binwiederhier