[GH-ISSUE #582] What's the right way to upload a minor version in 'semver'? #2155

Closed
opened 2026-04-20 10:07:49 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @SangHakLee on GitHub (Jun 19, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/582

There are two ways.

My thoughts are: (way-1)

current version is 1.10.5
and there was a minor version update, so it was changed to 1.11.0

The following cases are the same.

  • major 1.10.5 -> 2.0.0
  • patch 1.10.5 -> 1.10.6

However, other team members think so: (way-2)

current version is 1.10.5
and there was a minor version update, so it was changed to 1.11.5


Which of way-1 and way-2 is more suitable for semver?

Originally created by @SangHakLee on GitHub (Jun 19, 2020). Original GitHub issue: https://github.com/semver/semver/issues/582 There are two ways. My thoughts are: (`way-1`) > current version is **1.10.5** > and there was a minor version update, so it was changed to **1.11.0** > > The following cases are the same. > - `major` **1.10.5** -> **2.0.0** > - `patch` **1.10.5** -> **1.10.6** However, other team members think so: (`way-2`) > current version is **1.10.5** > and there was a minor version update, so it was changed to **1.11.5** --- Which of `way-1` and `way-2` is more suitable for semver?
GiteaMirror added the question label 2026-04-20 10:07:49 -05:00
Author
Owner

@ljharb commented on GitHub (Jun 19, 2020):

Absolutely way-1. The spec explicitly says this here: https://semver.org/#spec-item-7

Patch version MUST be reset to 0 when minor version is incremented.

<!-- gh-comment-id:646454394 --> @ljharb commented on GitHub (Jun 19, 2020): Absolutely way-1. The spec explicitly says this here: https://semver.org/#spec-item-7 > Patch version MUST be reset to 0 when minor version is incremented.
Author
Owner

@SangHakLee commented on GitHub (Jun 19, 2020):

@ljharb Thank you.

It was clearly stated in the document.
I should have read the document in more detail.


Additionally

Patch and minor version MUST be reset to 0 when major version is incremented.


It became clear and certain!

<!-- gh-comment-id:646459396 --> @SangHakLee commented on GitHub (Jun 19, 2020): @ljharb Thank you. It was clearly stated in the document. I should have read the document in more detail. --- **Additionally** > Patch and minor version MUST be reset to 0 when major version is incremented. --- **It became clear and certain!**
Author
Owner

@alexandrtovmach commented on GitHub (Jun 19, 2020):

@ljharb thanks for answer 👍
@SangHakLee Closing as solved, feel free to re-open if there are still any questions

<!-- gh-comment-id:646829282 --> @alexandrtovmach commented on GitHub (Jun 19, 2020): @ljharb thanks for answer 👍 @SangHakLee Closing as solved, feel free to re-open if there are still any questions
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#2155