Semantic-release plugin to generate changelog content with conventional-changelog
{
"context": "Evaluates how the solution uses @semantic-release/release-notes-generator to load a conventional-changelog preset/config, merge parser/writer overrides, and rely on the plugin's native behaviors instead of reimplementing them.",
"type": "weighted_checklist",
"checklist": [
{
"name": "GenerateNotes usage",
"description": "Invokes the package's `generateNotes` hook (via the exported plugin function) to produce the changelog instead of reproducing conventional-changelog logic manually.",
"max_score": 20
},
{
"name": "Preset selection",
"description": "Passes the provided preset name into the plugin (`preset` option) and supports loading a preset module via `config` or `presetConfig` for file-based configs, letting the package resolve presets itself.",
"max_score": 20
},
{
"name": "Parser overrides merge",
"description": "Supplies `parserOpts` with the custom note keywords while allowing the loaded preset's parser options to remain in effect (merging rather than replacing defaults).",
"max_score": 20
},
{
"name": "Writer overrides merge",
"description": "Provides `writerOpts` that remap commit types (e.g., chore -> Maintenance) while keeping the preset's other writer options intact, relying on the package's merge behavior.",
"max_score": 20
},
{
"name": "Defaults and errors",
"description": "Allows the package's default Angular preset to be used when no preset is supplied and surfaces preset resolution errors from the plugin (does not swallow/rewrite them).",
"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