Build metadata is a completely optional way to tack on metadata to a version that does not affect the public API or precedence while still be compliant with SemVer. It's similar to a comment.
This allows folks to build on additional meaning or behavior that's meaningful to their custom systems without making any claims about the public version. For example, folks might use it for cache busting, layering custom behavior on top of SemVer, bookkeeping to tie when and
where a build was made, etc.
This PR is related to #61 and supersedes PR #70. You can see the previous discussions over there.
🔄 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/77
**Author:** [@haacked](https://github.com/haacked)
**Created:** 3/13/2013
**Status:** ✅ Merged
**Merged:** 3/20/2013
**Merged by:** [@haacked](https://github.com/haacked)
**Base:** `master` ← **Head:** `build-metadata-identifier`
---
### 📝 Commits (7)
- [`57fd194`](https://github.com/semver/semver/commit/57fd19400f53b5d4559de4dcf6ede2e638250625) Updated to RC2, with new definition for build metadata.
- [`26e3cf8`](https://github.com/semver/semver/commit/26e3cf8523b798d7d03354d5197c09dadae7c6e3) Removed an extraneous slash
- [`13aaada`](https://github.com/semver/semver/commit/13aaadaadb0d572b59c84a9851540ed1caeea35f) Add description of build metadata
- [`5114f85`](https://github.com/semver/semver/commit/5114f8543aba8ed1244f09bb2612a3ea5738df49) Omit build metadata from precedence rules
- [`9c58295`](https://github.com/semver/semver/commit/9c5829561e2580e3c63e30c57aa48a88b2015f80) Removed the plus sign and added examples
- [`2629b7e`](https://github.com/semver/semver/commit/2629b7e09cbb0856cca8fd6e075e12139d353d76) Fixed grammar mistake
- [`3823b6a`](https://github.com/semver/semver/commit/3823b6a1e3c810cd8b3e5a4c727e3574e6071e50) Add space between "hypen" and regex.
### 📊 Changes
**1 file changed** (+16 additions, -15 deletions)
<details>
<summary>View changed files</summary>
📝 `semver.md` (+16 -15)
</details>
### 📄 Description
Build metadata is a completely optional way to tack on metadata to a version that does not affect the public API or precedence while still be compliant with SemVer. It's similar to a comment.
This allows folks to build on additional meaning or behavior that's meaningful to their custom systems without making any claims about the public version. For example, folks might use it for cache busting, layering custom behavior on top of SemVer, bookkeeping to tie when and
where a build was made, etc.
This PR is related to #61 and supersedes PR #70. You can see the previous discussions over there.
---
<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/77
Author: @haacked
Created: 3/13/2013
Status: ✅ Merged
Merged: 3/20/2013
Merged by: @haacked
Base:
master← Head:build-metadata-identifier📝 Commits (7)
57fd194Updated to RC2, with new definition for build metadata.26e3cf8Removed an extraneous slash13aaadaAdd description of build metadata5114f85Omit build metadata from precedence rules9c58295Removed the plus sign and added examples2629b7eFixed grammar mistake3823b6aAdd space between "hypen" and regex.📊 Changes
1 file changed (+16 additions, -15 deletions)
View changed files
📝
semver.md(+16 -15)📄 Description
Build metadata is a completely optional way to tack on metadata to a version that does not affect the public API or precedence while still be compliant with SemVer. It's similar to a comment.
This allows folks to build on additional meaning or behavior that's meaningful to their custom systems without making any claims about the public version. For example, folks might use it for cache busting, layering custom behavior on top of SemVer, bookkeeping to tie when and
where a build was made, etc.
This PR is related to #61 and supersedes PR #70. You can see the previous discussions over there.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.