NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm
npm, #2203 most downloaded on npm
Parse raw conventional commits.
Latest stable
7.1.4
Last release 21 days ago
01 Nov 2026
Release timing varies
gaps range from 8 days to 10 months
Most releases are documented
notes for 49 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
12 years old
70 releases · first in 2015
Drag across the ruler to compare, or tap a release to open it.
avoid mid-word and non-numeric issue refs ( #1571 ) ( dfa8b2d ), closes #1570
Your coding agent can read these notes before it upgrades. Set up the MCP server →
match reference actions as whole words
require colon and line start for note keywords (#1517) (92423a5), closes #1515
do not treat indented lines as footers (#1513) (c01c3c4), closes #1512
### Features * replace meow with argue-cli
point package homepages and docs to documentation website
packages now require Node.js 22 or newer.
support RegExp in noteKeywords, issuePrefixes, and referenceActions (#1441) (f84bfc4), closes #1436
deduplicate references when the same issue appears multiple times
support ClickUp-style issue IDs ending with letters
named capturing groups support for regex patterns
conventional-commits-parser: allow @ in scope part of the header
deps: update dependency through2 to v4
Bumper exported class (#1218)Bumper exported class (#1218) (0ddc8cd)fix semver vulnerability (#1071) (3f5c99d), closes #1019
drop lodash from dependencies where it possible
support BREAKING-CHANGE alongside BREAKING CHANGE
### Bug Fixes * address ReDoS issue
conventional-commits-parser: address CVE-2021-23425
handle missing header in merge commit
Features replace semver with verkit
deps: update yargs-parser to move off a flagged-vulnerable version.
### Bug Fixes * add types for cli flags
conventional-commits-parser: add breaking change notes if header match breakingHeaderPattern
conventional-commits-parser: downgrade is-text-path due to node 6 incompatibility
Nothing published for this version
deps: update dependency is-text-path to v2
deps: update dependency through2 to v3
Upgrade to Lerna 3, fix Node.js v11 error
<a name="3.0.0"></a>
<a name="2.1.7"></a>
Nothing published for this version
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.6"></a>
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.5"></a>
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.4"></a>
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.3"></a>
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.2"></a>
Note: Version bump only for package conventional-commits-parser
Note: Version bump only for package conventional-commits-parser
<a name="2.1.1"></a>
always parse references (e84a9ae), closes #248
Nothing published for this version
…as `js { title: 'BREAKING AMEND', text: 'some breaking change' } ` The detection of notes, closes, continueNote and isBody are mutually exclusive.
<a name="2.0.0"></a>
breaks to notes (5189a61), closes #2options (eea319a)headerCorrespondence and improve commit parts (aca9e95), closes #6pull request should be merge. Also make the parsed result to be consistent with other parts.headerParts does not limit to type, scope and subject. They can now be defined in options.headerCorrespondence and the order is the order of capturing group in options.headerPattern. If part is missing in options.headerCorrespondence it is undefined. If part is not captured but is not missing in options.headerCorrespondence it is null.maxSubjectLength is not available any more.options.referenceKeywords is now options.referenceActionscloses now becomes references and it is loosely based the links above.notes object is no longer a key-value object but an array of note object, such as{
title: 'BREAKING AMEND',
text: 'some breaking change'
}
The detection of notes, closes, continueNote and isBody are mutually exclusive.
breaks changes to notes, because "Important Notes" a more generic term. There is no functional changes.<a name="1.3.0"></a>
<a name="1.2.3"></a>
Nothing published for this version
format references in breaking change notes ( #1529 ) ( a8ef1ed ), closes #631
regex: do not treat it as note if there are texts after keywords
<a name="1.2.2"></a>
regex: make getReferencePartsRegex stricter (b8a9fda), closes #27 (#30 #27 #28
mention: fix mention matching (43b32e7), closes #26
Nothing published for this version
Nothing published for this version
note: noteKeywords is case insensitive (4442b86), closes #21
<a name="1.0.0"></a>
<a name="0.2.0"></a>
<a name="0.1.2"></a>
cli: print the stack if verbose
options.config is added.releaseCount: replace allBlocks
pkg.transform: transform should be performed before normalizing pkgData
newlines: preserve newlines in a part (beb3d05), closes #15
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
git: generate the correct cmd of git log when there is no tags (dcd7551), closes #47 #48
log: correct out put for options.from and options.to (31ddb11), closes #47
writeLog: fix require statement for Writer
err: remove an extra error sentence
<a> if options.repository provided (7cb5cb5), closes #26Nothing published for this version
changelog: make version links work correctly
One column per quarter.