Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: support BREAKING-CHANGE alongside BREAKING CHANGE #882

Merged

Conversation

jeandeaual
Copy link
Contributor

I noticed a discrepancy between the default configuration of the conventional-changelog-conventionalcommits and conventional-commits-parser packages and the Conventional Commits specification.

As mentioned in the Conventional Commits v1.0.0 specification paragraph 16: “BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.”

jeandeaual and others added 2 commits December 18, 2021 12:57
…king changes

As mentioned in https://www.conventionalcommits.org/en/v1.0.0/#specification paragraph 16: “BREAKING-CHANGE MUST be synonymous with BREAKING CHANGE, when used as a token in a footer.”
@bcoe
Copy link
Member

bcoe commented Dec 25, 2021

@jeandeaual this seems like a good fix, but it seems to be breaking some tests.

@jeandeaual
Copy link
Contributor Author

@jeandeaual this seems like a good fix, but it seems to be breaking some tests.

@bcoe Sorry for that, it should be be fine now.

@bcoe bcoe merged commit e6f44ad into conventional-changelog:master Dec 29, 2021
@bcoe
Copy link
Member

bcoe commented Dec 29, 2021

@jeandeaual thank you for the great contribution 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants