conventional-changelog ember preset

Usage no npm install needed!

<script type="module">
  import conventionalChangelogEmber from '';


NPM version"> Build Status Dependency Status Coverage Status

conventional-changelog ember preset

Issues with the convention itself should be reported on the Ember issue tracker.

Ember Convention

Please use an appropriate commit prefix. If your pull request fixes an issue specify it in the commit message. Some examples:

[DOC beta] Update for commit prefixes
[FEATURE query-params-new] Message
[BUGFIX beta] Message
[SECURITY CVE-111-1111] Message

Commit Tagging

All commits should be tagged. Tags are denoted by square brackets ([]) and come at the start of the commit message.

Tag should not be confused with git tag. Message should not be confused with git commit message.

Bug Fixes

In general bug fixes are pulled into the beta branch. As such, the prefix is: [BUGFIX beta]. If a bug fix is a serious regression that requires a new patch release, [BUGFIX release] can be used instead.

For bugs related to canary features, follow the prefixing rules for features.


Cleanup commits are for removing deprecated functionality and should be tagged as [CLEANUP beta].


All additions and fixes for features in canary should be tagged as [FEATURE name] where name is the same as the flag for that feature.


Documentation commits are tagged as [DOC channel] where channel is canary, beta, or release. If no release is provided canary is assumed. The channel should be the most stable release that this documentation change applies to.


Security commits will be tagged as [SECURITY cve]. Please do not submit security related PRs without coordinating with the security team. See the Security Policy for more information.


In general almost all commits should fall into one of these categories. In the cases where they don't please submit your PR untagged. An Ember contributor will let you know if tagging is required.

Based on