[PR #561] [MERGED] feat!: support promoting pre-release versions to 1.0 #6341

New Issue

GiteaMirror · 2026-05-12T18:08:58-05:00

GiteaMirror commented

2026-05-12 18:08:58 -05:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/561
Author: @apff
Created: 1/10/2024
Status: ✅ Merged
Merged: 3/27/2024
Merged by: @stevemao

Base: master ← Head: promoting-from-pre-release

📝 Commits (1)

be6cc86 feat!: support promoting pre-release versions to 1.0

📊 Changes

1 file changed (+29 additions, -6 deletions)

View changed files

📝 content/next/index.md (+29 -6)

📄 Description

This solution is based on PR #214, to address Issue #165

While PR #214 describes a new footer INITIAL STABLE RELEASE:, here we also propose a short-hand !! syntax.

Closing this vacuum on how to deal with pre-release versions will allow automated tools to be able to deal with moving on from 0.Y.Z to 1.0.0.

_{🔄 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/conventional-commits/conventionalcommits.org/pull/561 **Author:** [@apff](https://github.com/apff) **Created:** 1/10/2024 **Status:** ✅ Merged **Merged:** 3/27/2024 **Merged by:** [@stevemao](https://github.com/stevemao) **Base:** `master` ← **Head:** `promoting-from-pre-release` --- ### 📝 Commits (1) - [`be6cc86`](https://github.com/conventional-commits/conventionalcommits.org/commit/be6cc86efd59ccc0c410fd06e1a3ff2389a3bbac) feat!: support promoting pre-release versions to 1.0 ### 📊 Changes **1 file changed** (+29 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `content/next/index.md` (+29 -6) </details> ### 📄 Description This solution is based on PR #214, to address Issue #165 While PR #214 describes a new footer `INITIAL STABLE RELEASE:`, here we also propose a short-hand `!!` syntax. Closing this vacuum on how to deal with pre-release versions will allow automated tools to be able to deal with moving on from 0.Y.Z to 1.0.0. --- <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-05-12 18:08:58 -05:00

GiteaMirror closed this issue

2026-05-12 18:09:00 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#6341