[GH-ISSUE #278] breaking change does not bump major #5863

Closed
opened 2026-05-12 17:51:22 -05:00 by GiteaMirror · 3 comments
Owner

Originally created by @ashton on GitHub (Jun 15, 2020).
Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/278

Hello! I'm using lerna version with --conventional-commits option, and following the description on your website for a breaking change, copying and pasting the same commit message does not generates a major bump:

image

image

The changelog is generated correctly with the breaking change section
image

Originally created by @ashton on GitHub (Jun 15, 2020). Original GitHub issue: https://github.com/conventional-commits/conventionalcommits.org/issues/278 Hello! I'm using lerna version with --conventional-commits option, and following the description on your website for a breaking change, copying and pasting the same commit message does not generates a major bump: ![image](https://user-images.githubusercontent.com/95974/84699961-d24c7480-af28-11ea-9e1e-07f21bd620bd.png) ![image](https://user-images.githubusercontent.com/95974/84700026-ea23f880-af28-11ea-90f4-ec5cb20db572.png) The changelog is generated correctly **with** the breaking change section ![image](https://user-images.githubusercontent.com/95974/84700357-68809a80-af29-11ea-9c11-b047770a8010.png)
Author
Owner

@mainrs commented on GitHub (Jul 27, 2020):

Shouldn't this go into the repository of the tooling instead of the specification?

<!-- gh-comment-id:664213553 --> @mainrs commented on GitHub (Jul 27, 2020): Shouldn't this go into the repository of the tooling instead of the specification?
Author
Owner

@wesleytodd commented on GitHub (Sep 30, 2020):

Hey @ashton, I would recommend raising this issue on the lerna repo or the conventional changelog repo as @SirWindfield suggests.

<!-- gh-comment-id:701475503 --> @wesleytodd commented on GitHub (Sep 30, 2020): Hey @ashton, I would recommend raising this issue on the lerna repo or the conventional changelog repo as @SirWindfield suggests.
Author
Owner

@jak-pan commented on GitHub (Feb 28, 2021):

I guess that this is expected since per https://semver.org versions starting with 0.x.x are considered pre-release and during that period anything can change until you release a first stable version starting with 1.0.0 @ashton

<!-- gh-comment-id:787423734 --> @jak-pan commented on GitHub (Feb 28, 2021): I guess that this is expected since per https://semver.org versions starting with 0.x.x are considered pre-release and during that period anything can change until you release a first stable version starting with 1.0.0 @ashton
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#5863