github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-07-11 05:12:48 -05:00
Code Issues 1.0k Packages Projects Releases 4 Wiki Activity

[GH-ISSUE #45] Dashes in pre-release and build version #5152

New Issue
Closed
opened 2026-06-15 11:05:34 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-06-15 11:05:34 -05:00
Owner
Copy Link

Originally created by @sunsided on GitHub (Aug 30, 2012).
Original GitHub issue: https://github.com/semver/semver/issues/45

2.0.0-rc.1 states in §10 and §11 that " Identifiers MUST be comprised of only ASCII alphanumerics and dash [0-9A-Za-z-]". This suggests that the pre-release or build part may contain a dash. Since there is no fixed order defined for these parts (apart from precedence calculation in §12), either 0.1.2-alpha-2+b232-3 and 0.1.2+b232-3-alpha-2 would be considered valid, making it impossible to distinguish the version parts.

Originally created by @sunsided on GitHub (Aug 30, 2012). Original GitHub issue: https://github.com/semver/semver/issues/45 2.0.0-rc.1 states in §10 and §11 that " Identifiers MUST be comprised of only ASCII alphanumerics and dash `[0-9A-Za-z-]`". This suggests that the pre-release or build part may contain a dash. Since there is no fixed order defined for these parts (apart from precedence calculation in §12), either `0.1.2-alpha-2+b232-3` and `0.1.2+b232-3-alpha-2` would be considered valid, making it impossible to distinguish the version parts.
GiteaMirror commented 2026-06-15 11:05:35 -05:00
Author
Owner
Copy Link

@lukaszmoroz commented on GitHub (Aug 30, 2012):

"9. A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version."

Emphasis mine. The pre-release part must be first, so there is no ambiguity.

<!-- gh-comment-id:8173992 --> @lukaszmoroz commented on GitHub (Aug 30, 2012): "9. A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers **immediately following the patch version**." Emphasis mine. The pre-release part must be first, so there is no ambiguity.
GiteaMirror commented 2026-06-15 11:05:35 -05:00
Author
Owner
Copy Link

@sunsided commented on GitHub (Sep 1, 2012):

You're right.

<!-- gh-comment-id:8214443 --> @sunsided commented on GitHub (Sep 1, 2012): You're right.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
consensus seeking
duplicate
extend
layout
pull-request
Mirrored from GitHub Pull Request
 question
RFC
spelling/grammar
staled
update
waiting for PR
won't fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#5152
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?