[PR #519] [RFC] New post release syntax / change for build metadata syntax #2553

New Issue

GiteaMirror · 2026-04-20T10:30:28-05:00

GiteaMirror commented

2026-04-20 10:30:28 -05:00

📋 Pull Request Information

Original PR: https://github.com/semver/semver/pull/519
Author: @sylr
Created: 5/28/2019
Status: 🔄 Open

Base: master ← Head: post-release-syntax

📝 Commits (2)

f4a44b3 New post release syntax / change for build metadata syntax
8aa510a Merge branch 'master' into post-release-syntax

📊 Changes

1 file changed (+26 additions, -8 deletions)

View changed files

📝 semver.md (+26 -8)

📄 Description

A post release syntax is useful for hot fix versions and for people maintaining patch sets on top of official versions that did not make it to the official release (whether is hasn't made the cut or because it has been refused).

According to me the most logical syntax for post-release is to use the + sign. As it is already used for build metadata in v2.0.0 I'm suggesting to change build metadata separtor to the ~ sign.

Example: 1.15.3+patchset.1~go1.11, 1.15.3+patchset.1~go1.12

Real life example: linux-4.4.190+rt.187 -> linux kernel 4.4.190 with RT patch version 187.

The downside of this is that would be a breaking change.

EDIT: Change example to use patchset instead of hotfix which is confusing as hotfix automatically yields patch version increment (one quickly forgets that this RFC aims to enabled non official releases from people who needs to manage their own patch sets).

_{🔄 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/519 **Author:** [@sylr](https://github.com/sylr) **Created:** 5/28/2019 **Status:** 🔄 Open **Base:** `master` ← **Head:** `post-release-syntax` --- ### 📝 Commits (2) - [`f4a44b3`](https://github.com/semver/semver/commit/f4a44b3b80fbd0d54db68f0e14e3ae33f58a011b) New post release syntax / change for build metadata syntax - [`8aa510a`](https://github.com/semver/semver/commit/8aa510a2ff53dab91935a031f74ecbd36edf2e50) Merge branch 'master' into post-release-syntax ### 📊 Changes **1 file changed** (+26 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `semver.md` (+26 -8) </details> ### 📄 Description A post release syntax is useful for hot fix versions and for people maintaining patch sets on top of official versions that did not make it to the official release (whether is hasn't made the cut or because it has been refused). According to me the most logical syntax for post-release is to use the `+` sign. As it is already used for build metadata in v2.0.0 I'm suggesting to change build metadata separtor to the `~` sign. Example: `1.15.3+patchset.1~go1.11`, `1.15.3+patchset.1~go1.12` Real life example: `linux-4.4.190+rt.187` -> [linux kernel 4.4.190 with RT patch version 187.](https://rt.wiki.kernel.org/index.php/Main_Page) The downside of this is that would be a breaking change. EDIT: Change example to use `patchset` instead of `hotfix` which is confusing as hotfix automatically yields patch version increment (one quickly forgets that this RFC aims to enabled non official releases from people who needs to manage their own patch sets). --- <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-04-20 10:30:28 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/semver#2553