Semantic-release plugin to generate changelog content with conventional-changelog
{
"context": "Evaluates how the solution drives @semantic-release/release-notes-generator to emit custom release notes using presetConfig along with parserOpts and writerOpts overrides for section mapping, detection, and ordering.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Preset sections",
"description": "Invokes generateNotes with a presetConfig.types map that assigns feat -> \"Features\", fix -> \"Bug Fixes\", and perf -> \"Performance Improvements\", and the rendered notes show those section titles for matching commits.",
"max_score": 30
},
{
"name": "Parser override",
"description": "Supplies parserOpts (e.g., headerPattern/headerCorrespondence or noteKeywords) so bracketed messages like \"[Perf] Trim startup costs\" are parsed with type \"perf\" and flow into the perf section rather than being dropped.",
"max_score": 25
},
{
"name": "Writer ordering",
"description": "Uses writerOpts (such as commitGroupsSort/order or a transform) to enforce section order of Performance Improvements first, then Features, then Bug Fixes in the generated Markdown.",
"max_score": 25
},
{
"name": "Filters unmapped",
"description": "Relies on writerOpts.transform or equivalent to merge with the preset so unmapped types (e.g., chores) are omitted and empty sections are not rendered in the output.",
"max_score": 20
}
]
}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