semantic-release / semantic-release/commit-analyzer
Upgrade conventionalcommits preset to v10
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
Hello,
It seems after fixing the issue conventional-changelog/conventional-changelog/issues/1476, new GitHub Releases do not contain Release Notes anymore.
Our setup is fairly simple:
.releaserc:
{
"branches": [
"main",
{
"name": "release/+([0-9])?(.{+([0-9]),x}).x",
"range": "${name.replace(/^release\\//g, '')}"
},
"next",
{ "name": "alpha", "prerelease": true },
{ "name": "beta", "prerelease": true },
{ "name": "rc", "prerelease": true }
],
"plugins": [
[
"@semantic-release/commit-analyzer",
{
"preset": "conventionalcommits"
}
],
[
"@semantic-release/release-notes-generator",
{
"preset": "conventionalcommits",
"presetConfig": {
"preset": {
"name": "conventionalchangelog"
}
}
}
],
"@semantic-release/github"
]
}
CI:
- name: Semantic Release
id: semantic_release
uses: cycjimmy/semantic-release-action@9246c0bd17405b1f20450501f39234912258bc50 #v6
with:
semantic_version: 25.0.5
dry_run: ${{ inputs.dryRun }}
extra_plugins: |
@semantic-release/changelog
@semantic-release/git
conventional-changelog-conventionalcommits
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
Setting the conventional-changelog-conventionalcommits to version v9.3.1 resolves the issue.
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 locating the dependency declaration for conventional-changelog-conventionalcommits and the release-related entry points; compare its current version with v10 and review the reported presetConfig shape. Confirm the change by running the relevant checks and verifying that generated GitHub Releases contain release notes again.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, javascript
- Domain
- ci-cd, release
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100