mathieudutour / mathieudutour/github-tag-action

Use conventionalcommits preset with @semantic-release/commit-analyzer

Open
#208 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
733
Forks
227
PR merge metrics
No merged PRs in 30d

Description

release-notes-generator uses conventionalcommits preset, but commit-analyzer doesn’t. This means changelogs and releases can end up out of sync.

For example, the following commit:
```
git commit -m 'feat!: do a major release'
```

…will generate a changelog like this:

```md
### ⚠ BREAKING CHANGES

* do a major release

### Features

* do a major release
```

…but the commit-analyzer output is:
```
Analyzing commit: feat!: do a major release
The commit should not trigger a release
```

The expected output is:
```
Analyzing commit: feat!: do a major release
The release type for the commit is major
```

Contributor guide

Open the contributing guide

Research direction

Start by locating the release-notes-generator and commit-analyzer configuration, then reproduce the issue with the example `feat!: do a major release` commit. Verify that both components use the conventionalcommits preset and that the analyzer reports a major release, matching the expected output.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, typescript
Domain
ci-cd, release
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.