📋 semantic-release plugin to generate changelog content with conventional-changelog
Installations
npm install @semantic-release/release-notes-generator
Developer Guide
Typescript
No
Module System
ESM
Min. Node Version
>=20.8.1
Node Version
22.12.0
NPM Version
10.9.2
Score
50.6
Supply Chain
85.5
Quality
84.6
Maintenance
100
Vulnerability
96.1
License
Releases
Contributors
Unable to fetch Contributors
Languages
JavaScript (100%)
Love this project? Help keep it running — sponsor us today! 🚀
Developer
semantic-release
Download Statistics
Total Downloads
221,632,752
Last Day
266,178
Last Week
1,592,222
Last Month
6,549,815
Last Year
69,460,708
GitHub Statistics
MIT License
324 Stars
698 Commits
49 Forks
6 Watchers
5 Branches
26 Contributors
Updated on Feb 15, 2025
Package Meta Information
Latest Version
14.0.3
Package Id
@semantic-release/release-notes-generator@14.0.3
Unpacked Size
33.45 kB
Size
5.79 kB
File Count
7
NPM Version
10.9.2
Node Version
22.12.0
Published on
Jan 03, 2025
Total Downloads
Cumulative downloads
Total Downloads
221,632,752
Last Day
4.5%
266,178
Compared to previous day
Last Week
3.4%
1,592,222
Compared to previous week
Last Month
32.7%
6,549,815
Compared to previous month
Last Year
36.7%
69,460,708
Compared to previous year
Daily Downloads
Weekly Downloads
Monthly Downloads
Yearly Downloads
Dependencies
10
Peer Dependencies
1
Dev Dependencies
20
release-notes-generator
semantic-release plugin to generate changelog content with conventional-changelog
Step | Description |
---|---|
generateNotes | Generate release notes for the commits added since the last release with conventional-changelog. |
Install
1$ npm install @semantic-release/release-notes-generator -D
Usage
The plugin can be configured in the semantic-release configuration file:
1{ 2 "plugins": [ 3 [ 4 "@semantic-release/commit-analyzer", 5 { 6 "preset": "angular", 7 "parserOpts": { 8 "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"] 9 } 10 } 11 ], 12 [ 13 "@semantic-release/release-notes-generator", 14 { 15 "preset": "angular", 16 "parserOpts": { 17 "noteKeywords": ["BREAKING CHANGE", "BREAKING CHANGES", "BREAKING"] 18 }, 19 "writerOpts": { 20 "commitsSort": ["subject", "scope"] 21 } 22 } 23 ] 24 ] 25}
With this example:
- the commits that contains
BREAKING CHANGE
,BREAKING CHANGES
orBREAKING
in their body will be considered breaking changes (by default the angular preset checks only forBREAKING CHANGE
andBREAKING CHANGES
) - the commits will be sorted in the changelog by
subject
thenscope
(by default the angular preset sort the commits in the changelog byscope
thensubject
)
Configuration
Options
Option | Description | Default |
---|---|---|
preset | conventional-changelog preset (possible values: angular , atom , codemirror , ember , eslint , express , jquery , jshint , conventionalcommits ). | angular |
config | NPM package name of a custom conventional-changelog preset. | - |
parserOpts | Additional conventional-commits-parser options that will extends the ones loaded by preset or config . This is convenient to use a conventional-changelog preset with some customizations without having to create a new module. | - |
writerOpts | Additional conventional-commits-writer options that will extends the ones loaded by preset or config . This is convenient to use a conventional-changelog preset with some customizations without having to create a new module. | - |
host | The host used to generate links to issues and commits. See conventional-changelog-writer#host. | The host from the repositoryurl option. |
linkCompare | Whether to include a link to compare changes since previous release in the release note. | true |
linkReferences | Whether to include a link to issues and commits in the release note. See conventional-changelog-writer#linkreferences. | true |
commit | Keyword used to generate commit links (formatted as <host>/<owner>/<repository>/<commit>/<commit_sha> ). See conventional-changelog-writer#commit. | commits for Bitbucket repositories, commit otherwise |
issue | Keyword used to generate issue links (formatted as <host>/<owner>/<repository>/<issue>/<issue_number> ). See conventional-changelog-writer#issue. | issue for Bitbucket repositories, issues otherwise |
presetConfig | Additional configuration passed to the conventional-changelog preset. Used for example with conventional-changelog-conventionalcommits. | - |
Notes: in order to use a preset
it must be installed (for example to use the eslint preset you must install it with npm install conventional-changelog-eslint -D
)
Note: config
will be overwritten by the values of preset
. You should use either preset
or config
, but not both.
Note: Individual properties of parserOpts
and writerOpts
will override ones loaded with an explicitly set preset
or config
. If preset
or config
are not set, only the properties set in parserOpts
and writerOpts
will be used.
Note: For presets that expects a configuration object, such as conventionalcommits
, the presetConfig
option must be set.

No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
30 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
all dependencies are pinned
Details
- Info: 6 out of 6 GitHub-owned GitHubAction dependencies pinned
Reason
all changesets reviewed
Reason
GitHub workflow tokens follow principle of least privilege
Details
- Info: topLevel 'contents' permission set to 'read': .github/workflows/release.yml:10
- Info: topLevel 'contents' permission set to 'read': .github/workflows/test.yml:13
- Info: no jobLevel write permissions found
Reason
license file detected
Details
- Info: project has a license file: LICENSE:0
- Info: FSF or OSI recognized license: MIT License: LICENSE:0
Reason
security policy file detected
Details
- Info: security policy file detected: github.com/semantic-release/.github/.github/SECURITY.md:1
- Info: Found linked content: github.com/semantic-release/.github/.github/SECURITY.md:1
- Info: Found disclosure, vulnerability, and/or timelines in security policy: github.com/semantic-release/.github/.github/SECURITY.md:1
- Info: Found text in security policy: github.com/semantic-release/.github/.github/SECURITY.md:1
Reason
packaging workflow detected
Details
- Info: Project packages its releases by way of GitHub Actions.: .github/workflows/release.yml:12
Reason
4 existing vulnerabilities detected
Details
- Warn: Project is vulnerable to: GHSA-x4c5-c7rf-jjgv
- Warn: Project is vulnerable to: GHSA-h5c3-5r3r-rr8q
- Warn: Project is vulnerable to: GHSA-rmvr-2pp2-xj38
- Warn: Project is vulnerable to: GHSA-xx4v-prfh-6cgc
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
- Warn: no fuzzer integrations found
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
- Warn: 0 commits out of 30 are checked with a SAST tool
Score
8
/10
Last Scanned on 2025-02-10
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn MoreOther packages similar to @semantic-release/release-notes-generator
@anolilab/semantic-release-preset
Semantic-release predefined presets.
@myparcel/semantic-release-release-notes-generator
semantic-release plugin to generate changelog content with conventional-changelog
@wrench/semantic-release-notes-generator
Semantic Release plugin allowing to regenerate changelog
@jeromefitz/release-notes-generator
Custom Release Note Generator for Semantic Release.