Semantic-release plugin to generate changelog content with conventional-changelog
{
"context": "Evaluates whether release notes are built with @semantic-release/release-notes-generator while exercising its handling of varied repository URLs (ssh, git+http, CodeCommit) and tag-driven compare links. Checks that solutions rely on the plugin's URL parsing instead of custom link construction.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Plugin integration",
"description": "Changelog generation calls @semantic-release/release-notes-generator generateNotes instead of reimplementing parsing or writing logic.",
"max_score": 20
},
{
"name": "Tag compare link",
"description": "previousTag and currentTag are passed into generateNotes context so the plugin builds the compare URL rather than custom link assembly.",
"max_score": 20
},
{
"name": "SSH normalization",
"description": "An scp/ssh repositoryUrl like git@github.com:owner/repo.git is sent to generateNotes so its normalization produces https-based compare and commit links for that host.",
"max_score": 20
},
{
"name": "HTTP preserved",
"description": "A git+http repositoryUrl is provided to generateNotes and the resulting commit/compare links keep the http scheme (no forced https).",
"max_score": 20
},
{
"name": "CodeCommit tolerance",
"description": "A CodeCommit-style repositoryUrl (e.g., codecommit::eu-central-1://user@repo) is handled by generateNotes without errors, accepting the plugin's hash-only output when links cannot be built.",
"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