Skip to content
📖 PR-based changelog generator with monorepo support
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
bin cli: Wrap script in run() function Jul 12, 2017
.gitignore Update .gitignore file (#39) Mar 3, 2017
.npmignore Adjust ".npmignore" file Jun 6, 2017
.travis.yml TravisCI: Remove deprecated `sudo: false` option Dec 2, 2018
LICENSE Add LICENSE file Jun 19, 2018
tslint.json Use `tslint-plugin-prettier` to check for styling issues Jun 16, 2018


TravisCI Build Status Latest NPM release

PR-based changelog generator with monorepo support


Install with yarn:

yarn add lerna-changelog --dev
# or globally
yarn global add lerna-changelog

We're using yarn but you can use npm if you like:

npm install --save-dev lerna-changelog
# or globally
npm install --global lerna-changelog


$ lerna-changelog
## Unreleased (2018-05-24)

#### :bug: Bug Fix
* [#198]( Avoid an infinite loop ([@helpful-hacker](

#### :house: Internal
* [#183]( Standardize error messages ([@careful-coder](

#### Commiters: 2
- Helpful Hacker ([@helpful-hacker](
- [@careful-coder](

By default lerna-changelog will show all pull requests that have been merged since the latest tagged commit in the repository. That is however only true for pull requests with certain labels applied. The labels that are supported by default are:

  • breaking (💥 Breaking Change)
  • enhancement (🚀 Enhancement)
  • bug (🐛 Bug Fix)
  • documentation (📝 Documentation)
  • internal (🏠 Internal)

You can also use the --from and --to options to view a different range of pull requests:

lerna-changelog --from=v1.0.0 --to=v2.0.0

Monorepo support

If you have a packages folder and your projects in subfolders of that folder lerna-changelog will detect it and include the package names in the changelog for the relevant changes.

GitHub Token

Since lerna-changelog interacts with the GitHub API you may run into rate limiting issues which can be resolved by supplying a "personal access token":

export GITHUB_AUTH="..."

You'll need a personal access token for the GitHub API with the repo scope for private repositories or just public_repo scope for public repositories.


You can configure lerna-changelog in various ways. The easiest way is by adding a changelog key to the package.json file of your project:

  // ...
  "changelog": {
    "labels": {
      "feature": "New Feature",
      "bug": "Bug Fix"

The supported options are:

  • repo: Your "org/repo" on GitHub (automatically inferred from the package.json file)

  • nextVersion: Title for unreleased commits (e.g. Unreleased)

  • labels: GitHub PR labels mapped to changelog section headers

  • ignoreCommitters: List of committers to ignore (exact or partial match). Useful for example to ignore commits from bots.

  • cacheDir: Path to a GitHub API response cache to avoid throttling (e.g. .changelog)


lerna-changelog is released under the MIT License.

You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.