I omitted the free-form metadata component, as I wasn't sure what character set to allow within it, but I wanted to proceed with the new build metadata definition.
🔄 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/70
**Author:** [@jeffhandley](https://github.com/jeffhandley)
**Created:** 3/7/2013
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `master`
---
### 📝 Commits (4)
- [`a3e0e02`](https://github.com/semver/semver/commit/a3e0e02951187a4d8d5c7aabdc471afb847a4671) Updated to RC2, with new definition for build metadata.
- [`cd0a3de`](https://github.com/semver/semver/commit/cd0a3dec142be3138baa1ae473cfb76b230eb556) Removed an extraneous slash
- [`7dadf9a`](https://github.com/semver/semver/commit/7dadf9a3e531a77934a19be6fc5486bbb46c90eb) Expand the verbiage around build metadata purpose
- [`b9e08c6`](https://github.com/semver/semver/commit/b9e08c6beac710c6cb2b0d2a71d5d93d43eee15b) Clarify compatibility between versions with only differing build metadata
### 📊 Changes
**1 file changed** (+18 additions, -13 deletions)
<details>
<summary>View changed files</summary>
📝 `semver.md` (+18 -13)
</details>
### 📄 Description
Related to #61.
I omitted the free-form metadata component, as I wasn't sure what character set to allow within it, but I wanted to proceed with the new build metadata definition.
---
<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/70
Author: @jeffhandley
Created: 3/7/2013
Status: ❌ Closed
Base:
master← Head:master📝 Commits (4)
a3e0e02Updated to RC2, with new definition for build metadata.cd0a3deRemoved an extraneous slash7dadf9aExpand the verbiage around build metadata purposeb9e08c6Clarify compatibility between versions with only differing build metadata📊 Changes
1 file changed (+18 additions, -13 deletions)
View changed files
📝
semver.md(+18 -13)📄 Description
Related to #61.
I omitted the free-form metadata component, as I wasn't sure what character set to allow within it, but I wanted to proceed with the new build metadata definition.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.