This is cherry picked from #103 and attempts to clarify precedence.
This clarifies a couple of things.
How to compare pre-release versions with differing number of identifiers.
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>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 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)
9dcea3cSection 11: A larger set of pre-release is higher84c9618Attempt 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.
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.