Semantic-release plugin to generate changelog content with conventional-changelog
Build a utility that produces release notes from conventional commits while allowing callers to supply a preset and layer parser/writer overrides on top of that preset.
"angular" and a parser override that treats DEPRECATION as a note keyword, a commit containing DEPRECATION: drop v1 API in its body appears under the note heading with that body text. @testchore type to a Maintenance section via writer options, a chore: tidy docs commit appears under a ### Maintenance heading. @testfeat: add login yields a ### Features heading with a bullet for add login. @test@generates
/**
* Generate release notes from conventional commits using an optional preset or preset config path,
* allowing parser and writer overrides to merge with the loaded preset options.
*
* @param {Object} options
* @param {Array<{message: string, hash?: string, body?: string}>} options.commits - Conventional commits to include.
* @param {string} [options.preset] - Name of the conventional-changelog preset to load.
* @param {string} [options.presetConfigPath] - File path to a preset configuration module to load.
* @param {Object} [options.parserOverrides] - Parser option overrides applied on top of the preset defaults.
* @param {Object} [options.writerOverrides] - Writer option overrides applied on top of the preset defaults.
* @param {Object} [options.context] - Release context (version, previous tag, current tag, repo info).
* @returns {Promise<string>} Generated release notes text.
*/
export async function buildReleaseNotes(options);Produces changelog text from conventional commit data using conventional-changelog presets. @satisfied-by
tessl i tessl/npm-semantic-release--release-notes-generator@14.0.0docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10