github-starred/semver
2
0
Fork 0
mirror of https://github.com/semver/semver.git synced 2026-07-10 19:50:47 -05:00
Code Issues 1.0k Packages Projects Releases 4 Wiki Activity

[GH-ISSUE #28] development order and API compatibility are not the same #6012

New Issue
Closed
opened 2026-06-17 04:25:14 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-06-17 04:25:14 -05:00
Owner
Copy Link

Originally created by @Tieske on GitHub (May 27, 2012).
Original GitHub issue: https://github.com/semver/semver/issues/28

Currently the spec prescribes how to calculate precedence, but actually mixes this with development order.

The pre-release versions should not be taken into account when determining compatibility, because if you do, it requires updating the major/minor and patch numbers while working on new releases. If the alpha of 3.2.1 has a bug that is fixed in beta of 3.2.1, then it should have been labeled beta for 3.2.2 because of that bugfix.

To fix it; define 2 distinct precedence calculations;

  1. Development order: basically the current precedence calculation, including any pre-release tags
  2. API compatibility precedence: in this calculation any label that has a pre-release identifier (or a major version 0), should simply be ignored because no compatibility statements can be deduced from the numbers (yet), until it is released (hence the word 'pre-release').
Originally created by @Tieske on GitHub (May 27, 2012). Original GitHub issue: https://github.com/semver/semver/issues/28 Currently the spec prescribes how to calculate precedence, but actually mixes this with development order. The pre-release versions should not be taken into account when determining compatibility, because if you do, it requires updating the major/minor and patch numbers while working on new releases. If the alpha of 3.2.1 has a bug that is fixed in beta of 3.2.1, then it should have been labeled beta for 3.2.2 because of that bugfix. To fix it; define 2 distinct precedence calculations; 1. Development order: basically the current precedence calculation, including any pre-release tags 2. API compatibility precedence: in this calculation any label that has a pre-release identifier (or a major version 0), should simply be ignored because no compatibility statements can be deduced from the numbers (yet), until it is released (hence the word 'pre-release').
GiteaMirror commented 2026-06-17 04:25:15 -05:00
Author
Owner
Copy Link

@Tieske commented on GitHub (Jun 4, 2012):

Created a pull request under issue 30, see https://github.com/mojombo/semver/pull/30
Hence closing this issue.

<!-- gh-comment-id:6097684 --> @Tieske commented on GitHub (Jun 4, 2012): Created a pull request under issue 30, see https://github.com/mojombo/semver/pull/30 Hence closing this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
consensus seeking
duplicate
extend
layout
pull-request
Mirrored from GitHub Pull Request
 question
RFC
spelling/grammar
staled
update
waiting for PR
won't fix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/semver#6012
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?