[PR #214] [CLOSED] feat!: specify commit type semver bump effects #3013

New Issue

GiteaMirror · 2026-04-19T11:28:27-05:00

GiteaMirror commented

2026-04-19 11:28:27 -05:00

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/214
Author: @jasonkuhrt
Created: 10/16/2019
Status: ❌ Closed

Base: master ← Head: feat/bump-spec

📝 Commits (5)

dbb1d66 feat: specify commit type semver bump effects
a805adf spec when no fix commits
c685978 spec initial stable release
37b5377 spec valid ISR placement
7182775 example

📊 Changes

1 file changed (+15 additions, -0 deletions)

View changed files

📝 content/v1.0.0-beta.4/index.md (+15 -0)

📄 Description

Will close #165

This is a backwards compatible change because the the SHOULD qualifer is used rather than MUST. However, I am not sure the weaker form is desirable here.

ISR = INITIAL STABLE RELEASE the proposed indicator for transition from initial development phase to post initial development phase.

probably should spec how ISR and ! can play together nicely
resolve if we should qualify with SHOULD or MUST
update examples
update summary
update to reflect 1.0 spec as per comment below

_{🔄 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/214 **Author:** [@jasonkuhrt](https://github.com/jasonkuhrt) **Created:** 10/16/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `feat/bump-spec` --- ### 📝 Commits (5) - [`dbb1d66`](https://github.com/conventional-commits/conventionalcommits.org/commit/dbb1d663e75d5cde009e6759ff97dcdb1cffae2c) feat: specify commit type semver bump effects - [`a805adf`](https://github.com/conventional-commits/conventionalcommits.org/commit/a805adfe0cb78c6dcf4e78dc614f04ac8be3863a) spec when no fix commits - [`c685978`](https://github.com/conventional-commits/conventionalcommits.org/commit/c6859783e217d1b4c7a1284e20f4dfe61ed0198e) spec initial stable release - [`37b5377`](https://github.com/conventional-commits/conventionalcommits.org/commit/37b5377d0f215b557d2e9a1df156aee885dd3d3d) spec valid ISR placement - [`7182775`](https://github.com/conventional-commits/conventionalcommits.org/commit/7182775956eac9254362ca186299edb4f46aaea8) example ### 📊 Changes **1 file changed** (+15 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `content/v1.0.0-beta.4/index.md` (+15 -0) </details> ### 📄 Description Will close #165 This is a backwards compatible change because the the `SHOULD` qualifer is used rather than `MUST`. However, I am not sure the weaker form is desirable here. ISR = `INITIAL STABLE RELEASE` the proposed indicator for transition from initial development phase to post initial development phase. - [ ] probably should spec how ISR and `!` can play together nicely - [ ] resolve if we should qualify with `SHOULD` or `MUST` - [x] update examples - [ ] update summary - [ ] update to reflect 1.0 spec as per [comment below](https://github.com/conventional-commits/conventionalcommits.org/pull/214#issuecomment-552178546) --- <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-19 11:28:27 -05:00

GiteaMirror closed this issue

2026-04-19 11:28:31 -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#3013