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?
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.
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.
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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?
@ljharb commented on GitHub (Mar 9, 2022):
It is not a semver version unless it has three numbers; some things will take
1.5to imply1.5.0, others will take it to imply1.5.x, which are distinctly different results.@Calorion commented on GitHub (Mar 10, 2022):
I see. Could that be added to the FAQ?
@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.
@JohnTitor commented on GitHub (Aug 13, 2022):
@Calorion It'd take some time to be merged but feel free to send a PR.
@nngo commented on GitHub (Sep 11, 2025):
see also #782
@JohnTitor commented on GitHub (Sep 11, 2025):
Let's merge this into the above mentioned issue. Closing.