[GH-ISSUE #556] Is An API Needed To Use Semver? #6395

New Issue

GiteaMirror · 2026-06-17T05:09:32-05:00

GiteaMirror commented

2026-06-17 05:09:32 -05:00

Originally created by @Nyameliaaaa on GitHub (Mar 31, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/556

And If So, What Is The Usecase for x.y?

Originally created by @Nyameliaaaa on GitHub (Mar 31, 2020). Original GitHub issue: https://github.com/semver/semver/issues/556 And If So, What Is The Usecase for x.y?

GiteaMirror closed this issue

2026-06-17 05:09:32 -05:00

GiteaMirror commented

2026-06-17 05:09:33 -05:00

@jwdonahue commented on GitHub (Apr 2, 2020):

See #468 and the related links.

Strictly interpreting the spec, yes. That said, most developer use SemVer to version packages of interfaces and implementations. It's also used to version some apps.

@jwdonahue commented on GitHub (Apr 2, 2020): See #468 and the related links. Strictly interpreting the spec, yes. That said, most developer use SemVer to version packages of interfaces and implementations. It's also used to version some apps.

GiteaMirror commented

2026-06-17 05:09:33 -05:00

@Nyameliaaaa commented on GitHub (Apr 2, 2020):

What About Major/Minor In NonAPI Stuff (Apps where you can't use old versions)

@Nyameliaaaa commented on GitHub (Apr 2, 2020): What About Major/Minor In NonAPI Stuff (Apps where you can't use old versions)

GiteaMirror commented

2026-06-17 05:09:33 -05:00

@Nyameliaaaa commented on GitHub (Apr 3, 2020):

@jwdonahue

@Nyameliaaaa commented on GitHub (Apr 3, 2020): @jwdonahue

GiteaMirror commented

2026-06-17 05:09:34 -05:00

@jwdonahue commented on GitHub (Apr 3, 2020):

What about it? X.Y is not a SemVer string. The spec covers a specific syntax, semantics and precedence rules. It is mute on the infinite other possibilities.

Unless you have further questions, please close this thread at your earliest possible convenience.

@jwdonahue commented on GitHub (Apr 3, 2020): What about it? X.Y is not a SemVer string. The spec covers a specific syntax, semantics and precedence rules. It is mute on the infinite other possibilities. Unless you have further questions, please close this thread at your earliest possible convenience.

GiteaMirror commented

2026-06-17 05:09:34 -05:00

@trusktr commented on GitHub (Apr 14, 2020):

FYI, some tools (for example https://jspm.io) take x.y to mean the equivalent of ~x.y. For example, https://dev.jspm.io/react@16.3 loads React 16.3.2, while https://dev.jspm.io/react@16 loads React 16.13.1 (at the time I am writing this).

@trusktr commented on GitHub (Apr 14, 2020): FYI, some tools (for example https://jspm.io) take `x.y` to mean the equivalent of `~x.y`. For example, https://dev.jspm.io/react@16.3 loads React 16.3.2, while https://dev.jspm.io/react@16 loads React 16.13.1 (at the time I am writing this).

GiteaMirror commented

2026-06-17 05:09:35 -05:00

@trusktr commented on GitHub (Apr 14, 2020):

@jwdonahue Are things like ~ part of semver? I don't see it listed at https://semver.org.

@trusktr commented on GitHub (Apr 14, 2020): @jwdonahue Are things like `~` part of semver? I don't see it listed at https://semver.org.

GiteaMirror commented

2026-06-17 05:09:35 -05:00

@jwdonahue commented on GitHub (Apr 15, 2020):

@trusktr, no they are not. The spec is mute on range specifications. Various tools handle them differently. IMNSHO, modern set and interval notation (standard mathematics) is far superior to most of the squiggly, star and other hacks out there. Any tooling that doesn't use the [1.0.0, 2.0.0) form is broken by design.

@jwdonahue commented on GitHub (Apr 15, 2020): @trusktr, no they are not. The spec is mute on range specifications. Various tools handle them differently. IMNSHO, modern [set](https://en.wikipedia.org/wiki/Set_theory) and [interval](https://en.wikipedia.org/wiki/Interval_(mathematics)) notation (standard mathematics) is far superior to most of the squiggly, star and other hacks out there. Any tooling that doesn't use the `[1.0.0, 2.0.0)` form is broken by design.

GiteaMirror commented

2026-06-17 05:09:36 -05:00

@jwdonahue commented on GitHub (Apr 15, 2020):

@diligamer, unless you require further explanation, please close this thread at your earliest possible convenience. Thank you.

@jwdonahue commented on GitHub (Apr 15, 2020): @diligamer, unless you require further explanation, please close this thread at your earliest possible convenience. Thank you.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#6395