semantic-release / semantic-release/commit-analyzer
Adding ReleaseRules types list is working fine with release versioning but Changelog commits are empty.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
I've added to @semantic-release/commit-analyzer plugin a list of types under releaseRules:
module.exports = {
branches: [
'+([0-9])?(.{+([0-9]),x}).x',
'main',
'dev',
'master'
],
plugins: [
["@semantic-release/commit-analyzer", {
preset: "angular",
releaseRules: [
{type: "docs", release: "patch"},
{type: "refactor", release: "patch"},
{type: "ci", release: "patch"},
{type: "style", release: "patch"},
{type: "test", release: "patch"},
{type: "chore", release: "patch"}
]
}],
['@semantic-release/release-notes-generator', {
writerOpts: {
finalizeContext: function (context) {
return {
...context,
repository: 'myRepository',
owner: 'ownerName',
repoUrl: 'https://dev.azure.com',
commit: '_git/projectName/commit',
linkCompare: false
};
}
},
host: 'https://dev.azure.com',
issue: '_workitems/edit'
}],
'@semantic-release/changelog'
],
prepare: [
["@semantic-release/exec", {
"prepareCmd": 'echo ##vso[task.setvariable variable=nextRelease]${nextRelease.version}'
}],
'@semantic-release/changelog',
[
'@semantic-release/git',
{
message: 'ci(release): <%= nextRelease.version %> \n\n<%= nextRelease.notes %>'
}
]
]
};
It seems to be fine, when I make a commit of one of the types displayed in the list I can clearly see that release version is being increasing according to my definition.
But then I am looking at CHANGELOG.md file and it seems that commits are not being written and it left blanked.

Any idea what can cause this issue? I tried to search for a solution for this scenario few days and I feel I don't have any way to solve it by my own.
Can you tell me what is wrong with my script?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the shown release configuration, especially the @semantic-release/commit-analyzer, @semantic-release/release-notes-generator, and @semantic-release/changelog entries, alongside the blank CHANGELOG.md output. Reproduce the release with the listed commit types and determine which configuration or plugin interaction prevents commit entries from being generated; done means the relevant commits appear in CHANGELOG.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100