github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-12 02:17:21 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

[PR #175] [MERGED] chore: release 1.0.0 of specification #340

New Issue
Closed
opened 2026-02-17 11:59:46 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-17 11:59:46 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/175
Author: @bcoe
Created: 8/14/2019
Status: ✅ Merged
Merged: 9/30/2019
Merged by: @bcoe

Base: master ← Head: one-point-oh

📝 Commits (6)

📊 Changes

3 files changed (+258 additions, -14 deletions)

View changed files

📝 _redirects (+1 -1)
📝 content/next/index.md (+28 -13)
➕ content/v1.0.0/index.md (+229 -0)

📄 Description

I would like to advocate releasing version 1.0.0 of Conventional Commits.

Reasoning

  • we've been working on the project for ~3 years, and I think it's reached healthy maturity.
  • the specification is being used in the wild for a variety of major open source projects (yargs, electron, Istanbul) and folks seem happy.
  • we've seen adoption of Conventional Commits across a variety of languages (as an example we're using it for PHP, JavaScript, and Java at Google) demonstrating that the spec in its current form appeals to more than just JavaScript.
  • the convention has reached a healthy point of stability (since introducing ! (which is working great) there haven't been other major updates).

Let's Practice What We Preach

Releasing a 1.0.0 version of the specification doesn't mean that we can't iterate, it just means that we drop the ugly beta/alpha suffix and start following SemVer for updates to the specification.

CC: @tommywo, @jbottigliero

🔄 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/175 **Author:** [@bcoe](https://github.com/bcoe) **Created:** 8/14/2019 **Status:** ✅ Merged **Merged:** 9/30/2019 **Merged by:** [@bcoe](https://github.com/bcoe) **Base:** `master` ← **Head:** `one-point-oh` --- ### 📝 Commits (6) - [`8a2472c`](https://github.com/conventional-commits/conventionalcommits.org/commit/8a2472ca9103a2820973670856d216384908e7d2) chore: release 1.0 of specification - [`41f5176`](https://github.com/conventional-commits/conventionalcommits.org/commit/41f517695b673869c3f5e8b5d4dbebb317e748ab) chore: update v1.0.0 doc - [`9678e4b`](https://github.com/conventional-commits/conventionalcommits.org/commit/9678e4bc4c557a78927d0dee57f6368042604e13) docs: add missing ci - [`340c09e`](https://github.com/conventional-commits/conventionalcommits.org/commit/340c09e36f8c0e07df4548db874f19ab6101e76c) chore: address review - [`c0cfcff`](https://github.com/conventional-commits/conventionalcommits.org/commit/c0cfcff1b81b876d248fc3147f57db3e067dd896) chore: small copy edits - [`79d5240`](https://github.com/conventional-commits/conventionalcommits.org/commit/79d5240325b746cc98a5f1b6e161ccdbf33c2684) chore: smally copy tweak ### 📊 Changes **3 files changed** (+258 additions, -14 deletions) <details> <summary>View changed files</summary> 📝 `_redirects` (+1 -1) 📝 `content/next/index.md` (+28 -13) ➕ `content/v1.0.0/index.md` (+229 -0) </details> ### 📄 Description I would like to advocate releasing version `1.0.0` of Conventional Commits. ## Reasoning * we've been working on the project for ~3 years, and I think it's reached healthy maturity. * the specification is being used in the wild for a variety of major open source projects (yargs, electron, Istanbul) and folks seem happy. * we've seen adoption of Conventional Commits across a variety of languages (as an example we're using it for PHP, JavaScript, and Java at Google) demonstrating that the spec _in its current form_ appeals to more than just JavaScript. * the convention has reached a healthy point of stability (since introducing `!` (which is working *great*) there haven't been other major updates). ## Let's Practice What We Preach Releasing a `1.0.0` version of the specification doesn't mean that we can't iterate, it just means that we drop the ugly `beta`/`alpha` suffix and start following [SemVer](https://semver.org/) for updates to the specification. CC: @tommywo, @jbottigliero --- <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-02-17 11:59:46 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#340
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?