[GH-ISSUE #702] Regex from semver.org not matching 0.0.1-SNAPSHOT.I.0285680 #2208

New Issue

GiteaMirror · 2026-04-20T10:12:39-05:00

GiteaMirror commented

2026-04-20 10:12:39 -05:00

Originally created by @shoelzle on GitHub (May 14, 2021).
Original GitHub issue: https://github.com/semver/semver/issues/702

The version 0.0.1-SNAPSHOT.I.0285680 is not a valid semantic version.
The problem is the 0 after the dot, hence 0.0.1-SNAPSHOT.I.1285680 matches just fine.

But why must multiple digits in a numeric identifier not start with a zero ?

The relevant part from the semver.org BNF:

<numeric identifier> ::= "0"
                       | <positive digit>
                       | <positive digit> <digits>

Originally created by @shoelzle on GitHub (May 14, 2021). Original GitHub issue: https://github.com/semver/semver/issues/702 The version `0.0.1-SNAPSHOT.I.0285680` is not a valid semantic version. The problem is the `0` after the dot, hence `0.0.1-SNAPSHOT.I.1285680` matches just fine. But why must *multiple* digits in a numeric identifier not start with a zero ? The relevant part from the semver.org BNF: ``` <numeric identifier> ::= "0" | <positive digit> | <positive digit> <digits> ```

GiteaMirror closed this issue

2026-04-20 10:12:40 -05:00

GiteaMirror commented

2026-04-20 10:12:41 -05:00

@dtonhofer commented on GitHub (May 17, 2021):

I would say, because if it's a number, it should be written canonically, without any leading zeros.

@dtonhofer commented on GitHub (May 17, 2021): I would say, because if it's a number, it should be written canonically, without any leading zeros.

GiteaMirror commented

2026-04-20 10:12:42 -05:00

@shoelzle commented on GitHub (May 19, 2021):

My mistake:
The suffix 0285680 is an example of a short commit sha and as such it is just not semver compliant to put it in the pre-release part of the BNF because it is not a numeric identifier. But it is a build identifier, so the following versions are semver compliant:

0.0.1-SNAPSHOT+I.0285680
0.0.1-SNAPSHOT+I.1285680

Thanks for the hint.

@shoelzle commented on GitHub (May 19, 2021): My mistake: The suffix `0285680` is an example of a short commit sha and as such it is just not semver compliant to put it in the `pre-release` part of the BNF because it is not a `numeric identifier`. But it is a `build identifier`, so the following versions are semver compliant: * `0.0.1-SNAPSHOT+I.0285680` * `0.0.1-SNAPSHOT+I.1285680` Thanks for the hint.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#2208