bug: Invalid semver marked as valid

[mattfarina]

Try the version 1.0.0-dev.01 and it will show it is valid. Except the spec says of pre-releases:

Numeric identifiers MUST NOT include leading zeroes.

[trafium]

Could 01 possibly be interpreted as non-numeric prerelease version and thus valid?

UPD: I guess Identifiers consisting of only digits are compared numerically. rule says otherwise.

[vovtz]

Same goes for empty ‘identifiers’ (that’s what SemVer2 calls the parts between dots within the ‘prerelease’ field).

But this bug is more subtle too: although the version check field turns green with both of these invalid versions, the field below gives away that internally they are considered wrong (or cannot be processed at least), because it cannot tell what the next release version(s) will be.

[nikclayton]

1.0.5-rc+neko:240111.fd also reports as valid, but isn't (https://jubianchi.github.io/semver-check/#/version/1.0.5-rc%2Bneko%3A240111.fd). The : is not a valid character in build metadata.

pachli/pachli-android#372