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

[PR #108] [MERGED] Clarify version comparisons #742

New Issue
Closed
opened 2026-02-17 12:17:59 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-17 12:17:59 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/semver/semver/pull/108
Author: @haacked
Created: 6/10/2013
Status: ✅ Merged
Merged: 6/10/2013
Merged by: @haacked

Base: master ← Head: clarify-version-comparisons

📝 Commits (2)

  • 9dcea3c Section 11: A larger set of pre-release is higher
  • 84c9618 Attempt to clarify precedence even more.

📊 Changes

1 file changed (+15 additions, -7 deletions)

View changed files

📝 semver.md (+15 -7)

📄 Description

This is cherry picked from #103 and attempts to clarify precedence.

This clarifies a couple of things.

  1. How to compare pre-release versions with differing number of identifiers.
  2. How the left-to-right comparison of identifiers relates to the comparison of the whole version.

For example, while the following is implied because it's so obvious, SemVer never really made it clear that 1.9.0 < 2.1.1. It only specifies how each identifier is compared.

The second commit in this PR attempts to clarify how the comparison of each identifier relates to the comparison of the whole version. Does this seem necessary or is it implied elsewhere? Can the language be improved?

/cc @isaacs

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/semver/semver/pull/108 **Author:** [@haacked](https://github.com/haacked) **Created:** 6/10/2013 **Status:** ✅ Merged **Merged:** 6/10/2013 **Merged by:** [@haacked](https://github.com/haacked) **Base:** `master` ← **Head:** `clarify-version-comparisons` --- ### 📝 Commits (2) - [`9dcea3c`](https://github.com/semver/semver/commit/9dcea3c1702b5d1e4d511b282fbf4f078b76d5b7) Section 11: A larger set of pre-release is higher - [`84c9618`](https://github.com/semver/semver/commit/84c96182a5c89e77f6243396e90c963dde244598) Attempt to clarify precedence even more. ### 📊 Changes **1 file changed** (+15 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `semver.md` (+15 -7) </details> ### 📄 Description This is cherry picked from #103 and attempts to clarify precedence. This clarifies a couple of things. 1. How to compare pre-release versions with differing number of identifiers. 2. How the left-to-right comparison of identifiers relates to the comparison of the whole version. For example, while the following is implied because it's so obvious, SemVer never really made it clear that 1.9.0 < 2.1.1. It only specifies how each identifier is compared. The second commit in this PR attempts to clarify how the comparison of each identifier relates to the comparison of the whole version. Does this seem necessary or is it implied elsewhere? Can the language be improved? /cc @isaacs --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-17 12:17:59 -06:00
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 pull-request
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#742
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?