Original commit clarifies language around build metadata precedence:
"They're not the 'same version', necessarily, they're the same precedence"
Second commit clarifies a bit more.
Build metadata identifiers MUST not be empty.
Changed "are" to "have" when discussing version precedence. We usually say a version HAS a precedence not that it IS a precedence.
🔄 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/109
**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:** `build-metadata-clarification`
---
### 📝 Commits (3)
- [`e692c2f`](https://github.com/semver/semver/commit/e692c2f11347dea1442b3e5d831a9336970407d7) Section 10: Clarify language around build metadata precedence
- [`3071b5d`](https://github.com/semver/semver/commit/3071b5d2d59f4c768427ee3f6ec2ea16bdea4b2c) Clarify non-empty build metadata
- [`ec887c3`](https://github.com/semver/semver/commit/ec887c3b97e5eb36b17d47ce02925fa35b436ce3) Be more precise about version precedence
### 📊 Changes
**1 file changed** (+3 additions, -3 deletions)
<details>
<summary>View changed files</summary>
📝 `semver.md` (+3 -3)
</details>
### 📄 Description
Original commit clarifies language around build metadata precedence:
"They're not the 'same version', necessarily, they're the same precedence"
Second commit clarifies a bit more.
- Build metadata identifiers MUST not be empty.
- Changed "are" to "have" when discussing version precedence. We usually say a version HAS a precedence not that it IS a precedence.
---
<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/109
Author: @haacked
Created: 6/10/2013
Status: ✅ Merged
Merged: 6/10/2013
Merged by: @haacked
Base:
master← Head:build-metadata-clarification📝 Commits (3)
e692c2fSection 10: Clarify language around build metadata precedence3071b5dClarify non-empty build metadataec887c3Be more precise about version precedence📊 Changes
1 file changed (+3 additions, -3 deletions)
View changed files
📝
semver.md(+3 -3)📄 Description
Original commit clarifies language around build metadata precedence:
"They're not the 'same version', necessarily, they're the same precedence"
Second commit clarifies a bit more.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.