conventional-changelog-writer
Advanced tools
The conventional-changelog-writer npm package is a utility for generating changelogs based on commit messages that follow the Conventional Commits specification. It formats a changelog stream from parsed commit objects and allows customization of the output format.
Generate changelog
This code demonstrates how to use conventional-changelog-writer to generate a changelog from an array of commit objects. Each commit is written to the changelog stream, which formats them according to the specified context and options.
const writer = require('conventional-changelog-writer');
const commits = [
{hash: '123', type: 'feat', subject: 'add new feature'},
{hash: '456', type: 'fix', subject: 'fix bug'}
];
const context = {version: '1.0.0'};
const options = {};
const changelogStream = writer(context, options);
commits.forEach(commit => changelogStream.write(commit));
changelogStream.end();standard-version is a utility for versioning using semver and CHANGELOG generation powered by Conventional Commits. It automates version bumping and changelog generation, similar to conventional-changelog-writer, but also handles the creation of Git tags and commits.
lerna-changelog generates changelogs for monorepos managed by Lerna, based on pull requests and their labels. While it also focuses on changelog generation, it is specifically tailored for projects using Lerna and integrates with GitHub to enhance the changelog entries with PR links and author mentions.
Write logs based on conventional commits and templates
$ npm install --save conventional-changelog-writer
var conventionalChangelogWriter = require('conventional-changelog-writer');
conventionalChangelogWriter(context, options);
It returns a transform stream.
It expects an object mode upstream that looks something like this:
{ hash: '9b1aff905b638aa274a5fc8f88662df446d374bd',
header: 'feat(scope): broadcast $destroy event on scope destruction',
type: 'feat',
scope: 'scope',
subject: 'broadcast $destroy event on scope destruction',
body: null,
footer: 'Closes #1',
notes: [],
references: [ { action: 'Closes', owner: null, repository: null, issue: '1', raw: '#1' } ] }
{ hash: '13f31602f396bc269076ab4d389cfd8ca94b20ba',
header: 'feat(ng-list): Allow custom separator',
type: 'feat',
scope: 'ng-list',
subject: 'Allow custom separator',
body: 'bla bla bla',
footer: 'BREAKING CHANGE: some breaking change',
notes: [ { title: 'BREAKING CHANGE', text: 'some breaking change' } ],
references: [] }
Each chunk should be a commit. Json object is also valid. Parts of the objects will be formatted and combined into a log based on the handlebars context, templates and options.
The downstream might look something like this:
<a name="0.0.1"></a>
## 0.0.1 "this is a title" (2015-05-29)
### Features
* **ng-list:** Allow custom separator ([13f3160](https://github.com/a/b/commits/13f3160))
* **scope:** broadcast $destroy event on scope destruction ([9b1aff9](https://github.com/a/b/commits/9b1aff9)), closes [#1](https://github.com/a/b/issues/1)
### BREAKING CHANGES
* some breaking change
Returns a transform stream.
Variables that will be interpolated to the template. This object contains, but not limits to the following fields.
Type: string
Version number of the up-coming release. If version is found in the last commit before generating logs, it will be overwritten.
Type: string
Type: boolean Default: semver.patch(context.version) !== 0
By default, this value is true if version's patch is 0.
Type: string
The hosting website. Eg: 'https://github.com' or 'https://bitbucket.org'
Type: string
The owner of the repository. Eg: 'stevemao'.
Type: string
The repository name on host. Eg: 'conventional-changelog-writer'.
Type: boolean Default: true if repository, commit and issue are truthy
Should all references be linked?
Type: string Default: 'commits'
Commit keyword in the url if options.linkReferences === true.
Type: string Default: 'issues'
Issue or pull request keyword in the url if options.linkReferences === true.
Type: string Default: dateFormat(new Date(), 'yyyy-mm-dd', true)
Default to formatted ('yyyy-mm-dd') today's date. dateformat is used for formatting the date. If version is found in the last commit, committerDate will overwrite this.
Type: object
Type: object or function Default: get the first 7 digits of hash, and committerDate will be formatted as 'yyyy-mm-dd'.
Replace with new values in each commit.
If this is an object, the keys are paths to a nested object property. the values can be a string (static) and a function (dynamic) with the old value and path passed as arguments. This value is merged with your own transform object.
If this is a function, the commit chunk will be passed as the argument and the returned value would be the new commit object. This is a handy function if you can't provide a transform stream as an upstream of this one. If returns a falsy value this commit is ignored.
a raw object that is originally poured form upstream is attached to commit.
Type: string Default: 'type'
How to group the commits. EG: based on the same type. If this value is falsy, commits are not grouped.
Type: function, string or array Default: 'title'
A compare function used to sort commit groups. If it's a string or array, it sorts on the property(ies) by localeCompare. Will not sort if this is a falsy value.
The string can be a dot path to a nested object property.
Type: function, string or array Default: 'header'
A compare function used to sort commits. If it's a string or array, it sorts on the property(ies) by localeCompare. Will not sort if this is a falsy value.
The string can be a dot path to a nested object property.
Type: function, string or array Default: 'title'
A compare function used to sort note groups. If it's a string or array, it sorts on the property(ies) by localeCompare. Will not sort if this is a falsy value.
The string can be a dot path to a nested object property.
Type: function, string or array Default: 'text'
A compare function used to sort note groups. If it's a string or array, it sorts on the property(ies) by localeCompare. Will not sort if this is a falsy value.
The string can be a dot path to a nested object property.
Type: function, string or any Default: if commit.version is a valid semver.
When the upstream finishes pouring the commits it will generate a block of logs by default. However, you can generate more than one block based on this criteria (usually a version) even if there are still commits from the upstream.
####### commit
Current commit.
####### commits
Current collected commits.
####### context
The generated context based on original input context and options.
####### options
Normalized options.
NOTE: It checks on the transformed commit chunk instead of the original one (you can check on the original by access the raw object on the commit). However, if the transformed commit is ignored it falls back to the original commit.
If this value is a string, it checks the existence of the field. Set to other type to disable it.
Type: function Default: pass through
####### context
The generated context based on original input context and options.
####### options
Normalized options.
####### commits
Filtered commits from your git metadata.
####### keyCommit
The commit that triggers to generate the log.
Type: boolean Default: false
Are the commits from upstream in the reverse order? You should only worry about this when generating more than one blocks of logs based on generateOn. If you find the last commit is in the wrong block inverse this value.
Type: boolean Default: false
If this value is true, instead of emitting strings of changelog, it emits objects containing the details the block.
NOTE: The downstream must be in object mode if this is true.
Type: boolean Default: true
If true, reverted commits will be ignored.
Type: string Default: template.hbs
The main handlebars template.
Type: string Default: header.hbs
Type: string Default: commit.hbs
Type: string Default: footer.hbs
Type: object
Partials that used in the main template, if any. The key should be the partial name and the value should be handlebars template strings. If you are using handlebars template files, read files by yourself.
It is possible to customize this the changelog to suit your needs. Templates are written in handlebars. You can customize all partials or the whole template. Template variables are from either upstream or context. The following are a suggested way of defining variables.
Variables in upstream are commit specific and should be used per commit. Eg: commit date and commit username. You can think of them as "local" or "isolate" variables. A "raw" commit message (original commit poured from upstream) is attached to commit.
context should be module specific and can be used across the whole log. Thus these variables should not be related to any single commit and should be generic information of the module or all commits. Eg: repository url and author names, etc. You can think of them as "global" or "root" variables.
Basically you can make your own templates and define all your template context. Extra context are based on commits from upstream and options. For more details, please checkout handlebars and the source code of this module.
$ npm install --global conventional-changelog-writer
$ conventional-changelog-writer --help # for more details
It works with Line Delimited JSON.
If you have commits.ldjson
{"hash":"9b1aff905b638aa274a5fc8f88662df446d374bd","header":"feat(ngMessages): provide support for dynamic message resolution","type":"feat","scope":"ngMessages","subject":"provide support for dynamic message resolution","body":"Prior to this fix it was impossible to apply a binding to a the ngMessage directive to represent the name of the error.","footer":"BREAKING CHANGE: The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive.\nCloses #10036\nCloses #9338","notes":[{"title":"BREAKING CHANGE","text":"The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive."}],"references":[{"action":"Closes","owner",null,"repository":null,"issue":"10036","raw":"#10036"},{"action":"Closes","owner":null,"repository":null,"issue":"9338","raw":"#9338"}]}
And you run
$ conventional-changelog-writer commits.ldjson -o options.js
The output might look something like this
<a name="1.0.0"></a>
# 1.0.0 (2015-04-09)
### Features
* **ngMessages:** provide support for dynamic message resolution 9b1aff9, closes #10036 #9338
### BREAKING CHANGES
* The `ngMessagesInclude` attribute is now its own directive and that must be placed as a **child** element within the element with the ngMessages directive.
It is printed to stdout.
MIT © Steve Mao
FAQs
Write logs based on conventional commits and templates.
The npm package conventional-changelog-writer receives a total of 3,075,225 weekly downloads. As such, conventional-changelog-writer popularity was classified as popular.
We found that conventional-changelog-writer demonstrated a healthy version release cadence and project activity because the last version was released less than 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.
Security News
Elastic’s return to open source with the AGPL license has been met with skepticism, as many developers see it as a strategic move rather than a genuine effort to restore user trust and freedoms.
Security News
A new "revival hijack" supply chain attack targets deleted Python packages, with an estimated 22K packages at risk. Socket can detect and block hijacked packages that have added malicious code.
Product
We're introducing a new Analytics feature in the Socket dashboard so you can view changes in your organization's and repositories' alerts over time.