Create a change log for an npm project based on structured commit messages
Last updated 5 years ago by theludd .
ISC · Original npm · Tarball · package.json
$ cnpm install changeify 
SYNC missed versions from official npm registry.


Create a change log for an npm project based on structured commit messages.

How it works

Tag all your commit messages with either breaking, add, fix or doc and then before a release run changeify. Changeify will:

  1. Generate a changelog separated into the different sections
  2. Commit the changelog
  3. Bump the version based on the type of changes made since the last release (optional)
  4. Publish to npm (optional)
  5. Push to origin (optional)

Example commit message:

Change signature of function foo


The argument order was swithed because the new one is superior...

The tag "[breaking]" is case insensitive and can be placed anywhere in the commit message except for the header. The header is what will be included in the changelog. Look at the changelog of this project for an example.

All commits without any tags will be ignored when generating the change log and determening the new version.


Either the module globally and use it in any project or locally and add it as an npm script.

Run changeify -n for a dry run which will print the changelog and the next version to the console.

Run changeify to perform steps 1 and 2 mentioned above. Add flag -p --publish to also perform steps 3-5.

Current Tags

  • 0.1.2                                ...           latest (5 years ago)

4 Versions

  • 0.1.2                                ...           5 years ago
  • 0.1.1                                ...           5 years ago
  • 0.1.0                                ...           5 years ago
  • 0.0.2                                ...           5 years ago
Maintainers (1)
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 4
Dependencies (6)
Dev Dependencies (0)
Dependents (1)

Copyright 2014 - 2017 © |