Product
Introducing License Enforcement in Socket
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
lerna-changelog
Advanced tools
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](https://github.com/my-org/my-repo/pull/198) Avoid an infinite loop ([@helpful-hacker](https://github.com/helpful-hacker))
#### :house: Internal
* [#183](https://github.com/my-org/my-repo/pull/183) Standardize error messages ([@careful-coder](https://github.com/careful-coder))
#### Commiters: 2
- Helpful Hacker ([@helpful-hacker](https://github.com/helpful-hacker))
- [@careful-coder](https://github.com/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
(:boom: Breaking Change)enhancement
(:rocket: Enhancement)bug
(:bug: Bug Fix)documentation
(:memo: Documentation)internal
(:house: 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
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.
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.
FAQs
Generate a changelog for a lerna monorepo
The npm package lerna-changelog receives a total of 25,634 weekly downloads. As such, lerna-changelog popularity was classified as popular.
We found that lerna-changelog demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 4 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Product
Ensure open-source compliance with Socket’s License Enforcement Beta. Set up your License Policy and secure your software!
Product
We're launching a new set of license analysis and compliance features for analyzing, managing, and complying with licenses across a range of supported languages and ecosystems.
Product
We're excited to introduce Socket Optimize, a powerful CLI command to secure open source dependencies with tested, optimized package overrides.