[GH-ISSUE #900] Naming of major or minor version numbers #2301

New Issue

GiteaMirror · 2026-04-20T10:18:28-05:00

GiteaMirror commented

2026-04-20 10:18:28 -05:00

Originally created by @gowizzard on GitHub (Nov 30, 2022).
Original GitHub issue: https://github.com/semver/semver/issues/900

Hello everyone, I have a small understanding question and wanted to clarify this here briefly. If I have a higher version number, should it be major update or rather major >? The same would intressieren me also for smaller version numbers, whether one should write now minor downgrade or minor <.

Maybe someone here can answer this question. Thank you in advance.

Originally created by @gowizzard on GitHub (Nov 30, 2022). Original GitHub issue: https://github.com/semver/semver/issues/900 Hello everyone, I have a small understanding question and wanted to clarify this here briefly. If I have a higher version number, should it be `major update` or rather `major >`? The same would intressieren me also for smaller version numbers, whether one should write now `minor downgrade` or `minor <`. Maybe someone here can answer this question. Thank you in advance.

GiteaMirror closed this issue

2026-04-20 10:18:29 -05:00

GiteaMirror commented

2026-04-20 10:18:30 -05:00

@ljharb commented on GitHub (Nov 30, 2022):

"major version", i'd say.

@ljharb commented on GitHub (Nov 30, 2022): "major version", i'd say.

GiteaMirror commented

2026-04-20 10:18:32 -05:00

@gowizzard commented on GitHub (Nov 30, 2022):

Thank you, but what if I compare two versions? Then I would probably say major, minor or patch update. I have not found anything specific in the documentation.

Generally it's just about comparing different version numbers, which I implemented in a small project. I just want to make sure that my output is correct. Here you can find the example from my repository.

@gowizzard commented on GitHub (Nov 30, 2022): Thank you, but what if I compare two versions? Then I would probably say major, minor or patch update. I have not found anything specific in the documentation. Generally it's just about comparing different version numbers, which I implemented in a small project. I just want to make sure that my output is correct. [Here](https://github.com/gowizzard/compver#compare-versions) you can find the example from my repository.

GiteaMirror commented

2026-04-20 10:18:35 -05:00

@ljharb commented on GitHub (Nov 30, 2022):

If you compare two versions, i'd just indeed say "major/minor/patch update", or "major/minor/patch downgrade" (altho downgrades don't really happen often).

I'd suggest looking into https://npmjs.com/semver for an npm-specific example of comparison and ranges.

@ljharb commented on GitHub (Nov 30, 2022): If you compare two versions, i'd just indeed say "major/minor/patch update", or "major/minor/patch downgrade" (altho downgrades don't really happen often). I'd suggest looking into https://npmjs.com/semver for an npm-specific example of comparison and ranges.

GiteaMirror commented

2026-04-20 10:18:35 -05:00

@gowizzard commented on GitHub (Nov 30, 2022):

Okay, thank you! Then I have already installed the correct formulations.

@gowizzard commented on GitHub (Nov 30, 2022): Okay, thank you! Then I have already installed the correct formulations.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#2301