semantic-release / semantic-release/commit-analyzer
The `analyzeCommits` plugin configuration is invalid. Your configuration for the analyzeCommits plugin is ``.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 448
- Forks
- 82
- Avg merge
- 17h 41m
- Merged PRs (30d)
- 4
Description
Hello,
I'm trying to get this plugin working, however I'm always running into the error
What I tried so far was the .releaserc.json and package.json config types with both having the same results:
[10:30:43 AM] [semantic-release] › ✖ EPLUGINCONF The `analyzeCommits` plugin configuration is invalid.
The analyzeCommits plugin configuration (https://github.com/semantic-release/semantic-release/blob/master/docs/usage/plugins.md#analyzecommits-plugin) is required and must be a single or an array of plugins definition. A plugin definition is an npm module name, optionally wrapped in an array with an object.
Your configuration for the analyzeCommits plugin is ``.
AggregateError:
SemanticReleaseError: The `analyzeCommits` plugin configuration is invalid.
at module.exports (/home/user/workspace/my-app/node_modules/semantic-release/lib/get-error.js:6:10)
at /home/user/workspace/my-app/node_modules/semantic-release/lib/plugins/index.js:62:23
at Array.reduce (<anonymous>)
at module.exports (/home/user/workspace/my-app/node_modules/semantic-release/lib/plugins/index.js:47:59)
at module.exports (/home/user/workspace/my-app/node_modules/semantic-release/lib/get-config.js:84:35)
at async module.exports (/home/user/workspace/my-app/node_modules/semantic-release/index.js:265:32)
at async module.exports (/home/user/workspace/my-app/node_modules/semantic-release/cli.js:55:5)
at module.exports (/home/user/workspace/my-app/node_modules/semantic-release/lib/plugins/index.js:89:11)
at module.exports (/home/user/workspace/my-app/node_modules/semantic-release/lib/get-config.js:84:35)
at async module.exports (/home/user/workspace/my-app/node_modules/semantic-release/index.js:265:32)
This is my configuration
"dependencies": {
"semantic-release": "^19.0.5",
"conventional-changelog-conventionalcommits": "^5.0.0",
"@semantic-release/changelog": "^6.0.1",
"@semantic-release/commit-analyzer": "^9.0.2",
"@semantic-release/exec": "^6.0.3",
"@semantic-release/git": "^10.0.1",
"@semantic-release/github": "^8.0.6",
"@semantic-release/release-notes-generator": "^10.0.3",
},
"release": {
"preset": "conventionalcommits",
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/release-notes-generator",
"@semantic-release/changelog",
[
"@semantic-release/exec",
{
"publishCmd": "nx run affected --target=release --args=\"--version=${nextRelease.version}\""
}
]
]
},
What am I missing?
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 with the configuration validation path mentioned in lib/plugins/index.js and lib/get-config.js, then compare the reported package.json release configuration with the analyzeCommits plugin documentation. Reproduce the error using the versions and configuration shown; done means identifying whether the configuration is invalid or the validation/error reporting is incorrect, with coverage for the observed case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100