conventional-changelog/conventional-changelog

conventional-changelog-eslint 6.0.0 not matching commits when used in semantic-release

Closed this issue · 1 comments

anthony-nhs commented

Since upgrading conventional-changelog-eslint from 5.0.0 to 6.0.0 when being used in semantic-release (and so commit-analyzer) it is not correctly identifying commits.

This is the relevant section of our .releaserc file

            "@semantic-release/commit-analyzer",
            {
                "preset": "eslint",
                "releaseRules": [
                    {
                        "reminder": "Please update CONTRIBUTING.md if you change this",
                        "release": false
                    },
                    {
                        "tag": "Fix",
                        "release": "patch"
                    },
                    {
                        "tag": "Update",
                        "release": "patch"
                    },
                    {
                        "tag": "New",
                        "release": "minor"
                    },
                    {
                        "tag": "Breaking",
                        "release": "major"
                    },
                    {
                        "tag": "Docs",
                        "release": "patch"
                    },
                    {
                        "tag": "Build",
                        "release": false
                    },
                    {
                        "tag": "Upgrade",
                        "release": "patch"
                    },
                    {
                        "tag": "Chore",
                        "release": "patch"
                    }
                ]
            }

with 5.0.0 this is the output from semantic-release --dry-run --debug

[12:58:08 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[12:58:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Fix: [AEA-0000] - error if can not get next tag (#212)

## Summary

- Routine Change

### Details

- error if can not get next tag on merge to main
2024-05-07T12:58:08.701Z semantic-release:commit-analyzer Analyzing with custom rules
2024-05-07T12:58:08.702Z semantic-release:commit-analyzer The rule { tag: 'Fix', release: 'patch' } match commit with release type 'patch'
[12:58:08 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is patch

with 6.0.0 this is the output from semantic-release --dry-run --debug

[12:59:12 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[12:59:12 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: Fix: [AEA-0000] - error if can not get next tag (#212)

## Summary

- Routine Change

### Details

- error if can not get next tag on merge to main
2024-05-07T12:59:12.850Z semantic-release:commit-analyzer Analyzing with custom rules
2024-05-07T12:59:12.850Z semantic-release:commit-analyzer Analyzing with default rules
[12:59:12 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release