Semantic-release plugin to generate changelog content with conventional-changelog
{
"context": "Evaluates whether the solution leverages @semantic-release/release-notes-generator to normalize repository URLs into changelog link context, using its host-aware defaults and link toggles rather than custom parsing. Checks focus on invoking the plugin APIs that already handle URL normalization, host configuration, and compare/reference linking behaviors.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin parsing",
"description": "Uses generateNotes (or the underlying loadChangelogConfig flow) from @semantic-release/release-notes-generator to parse repositoryUrl instead of hand-rolled URL parsing.",
"max_score": 30
},
{
"name": "Host defaults",
"description": "Selects commit/issue path segments and reference settings based on HOSTS_CONFIG entries for the detected host (e.g., github/gitlab/bitbucket) before applying overrides.",
"max_score": 25
},
{
"name": "Protocol handling",
"description": "Relies on the plugin’s normalization to force https for ssh/git/https inputs while preserving explicit http schemes when present.",
"max_score": 15
},
{
"name": "Link toggles",
"description": "Passes linkCompare and linkReferences options through the plugin config so generated compare and reference links reflect the requested on/off toggles.",
"max_score": 15
},
{
"name": "Path overrides",
"description": "Honors commit and issue configuration overrides by forwarding them to @semantic-release/release-notes-generator instead of hardcoding link paths.",
"max_score": 15
}
]
}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