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

breaking change does not bump major #104

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

Originally created by @ashton on GitHub (Jun 15, 2020).

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). 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)
GiteaMirror commented 2026-02-17 11:46:15 -06:00
Author
Owner
Copy Link

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

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

@mainrs commented on GitHub (Jul 27, 2020): Shouldn't this go into the repository of the tooling instead of the specification?
GiteaMirror commented 2026-02-17 11:46:17 -06:00
Author
Owner
Copy Link

@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.

@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.
GiteaMirror commented 2026-02-17 11:46:18 -06:00
Author
Owner
Copy Link

@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

@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.
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
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#104
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?