[GH-ISSUE #813] Must every version include three numbers? #1399

Closed
opened 2026-04-16 10:48:48 -05:00 by GiteaMirror · 6 comments
Owner

Originally created by @Calorion on GitHub (Mar 9, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/813

It's long been common practice to leave the "patch" number off when it's zero, for instance "1.5" or "2.0", because it's more attractive in public-facing material. Is this prohibited in SemVer? And could this be added to the FAQ?

Originally created by @Calorion on GitHub (Mar 9, 2022). Original GitHub issue: https://github.com/semver/semver/issues/813 It's long been common practice to leave the "patch" number off when it's zero, for instance "1.5" or "2.0", because it's more attractive in public-facing material. Is this prohibited in SemVer? And could this be added to the FAQ?
Author
Owner

@ljharb commented on GitHub (Mar 9, 2022):

It is not a semver version unless it has three numbers; some things will take 1.5 to imply 1.5.0, others will take it to imply 1.5.x, which are distinctly different results.

<!-- gh-comment-id:1063082569 --> @ljharb commented on GitHub (Mar 9, 2022): It is not a semver version unless it has three numbers; some things will take `1.5` to imply `1.5.0`, others will take it to imply `1.5.x`, which are distinctly different results.
Author
Owner

@Calorion commented on GitHub (Mar 10, 2022):

I see. Could that be added to the FAQ?

<!-- gh-comment-id:1063565661 --> @Calorion commented on GitHub (Mar 10, 2022): I see. Could that be added to the FAQ?
Author
Owner

@ljharb commented on GitHub (Mar 10, 2022):

I’m not a maintainer here, but i suspect that a PR to add that, which is explicitly left open for as long as it takes before it’s merged (years, even), would be the best path to that outcome.

<!-- gh-comment-id:1063651933 --> @ljharb commented on GitHub (Mar 10, 2022): I’m not a maintainer here, but i suspect that a PR to add that, which is explicitly left open for as long as it takes before it’s merged (years, even), would be the best path to that outcome.
Author
Owner

@JohnTitor commented on GitHub (Aug 13, 2022):

@Calorion It'd take some time to be merged but feel free to send a PR.

<!-- gh-comment-id:1214168851 --> @JohnTitor commented on GitHub (Aug 13, 2022): @Calorion It'd take some time to be merged but feel free to send a PR.
Author
Owner

@nngo commented on GitHub (Sep 11, 2025):

see also #782

<!-- gh-comment-id:3279895965 --> @nngo commented on GitHub (Sep 11, 2025): see also #782
Author
Owner

@JohnTitor commented on GitHub (Sep 11, 2025):

Let's merge this into the above mentioned issue. Closing.

<!-- gh-comment-id:3279908253 --> @JohnTitor commented on GitHub (Sep 11, 2025): Let's merge this into the above mentioned issue. Closing.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#1399