Failed step "analyzeCommits" of plugin "[Function: ]"
See original GitHub issueWhen trying to run semantic-release -e semantic-release-monorepo --dry-run
With no release config in package.json
…
I run into the following error:
[23:25:21] [semantic-release] › ✖ Failed step "analyzeCommits" of plugin "[Function: ]"
[23:25:21] [semantic-release] › ✖ An error occurred while running semantic-release: TypeError: Expected `moduleId` to be of type `string`, got `object`
Here’s the full output:
[23:25:14] [semantic-release] › ℹ Running semantic-release version 15.13.30
[23:25:15] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[23:25:15] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/github"
[23:25:15] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[23:25:15] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[23:25:15] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[23:25:15] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[23:25:15] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[23:25:15] [semantic-release] › ⚠ Run automated release from branch master in dry-run mode
[23:25:19] [semantic-release] › ✔ Allowed to push to the Git repository
[23:25:19] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/npm"
[23:25:19] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/npm"
[23:25:19] [semantic-release] › ℹ Start step "verifyConditions" of plugin "@semantic-release/github"
[23:25:19] [semantic-release] [@semantic-release/github] › ℹ Verify GitHub authentication
[23:25:19] [semantic-release] › ✔ Completed step "verifyConditions" of plugin "@semantic-release/github"
[23:25:21] [semantic-release] › ℹ No git tag version found
[23:25:21] [semantic-release] › ℹ No previous release found, retrieving all commits
[23:25:21] [semantic-release] › ℹ Found 9 commits since last release
[23:25:21] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "[Function: ]"
[23:25:21] [semantic-release] › ✖ Failed step "analyzeCommits" of plugin "[Function: ]"
[23:25:21] [semantic-release] › ✖ An error occurred while running semantic-release: TypeError: Expected `moduleId` to be of type `string`, got `object`
at resolveFrom (/<path-to-project>/node_modules/resolve-from/index.js:11:9)
at module.exports (/<path-to-project>/node_modules/resolve-from/index.js:34:41)
at module.exports (/<path-to-project>/node_modules/semantic-release-plugin-decorators/node_modules/import-from/index.js:4:49)
at requirePlugin (/<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:4:33)
at resolvePluginFn (/<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:18:18)
at /<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:26:20
at validator (/<path-to-project>/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at /<path-to-project>/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
at next (/<path-to-project>/node_modules/p-reduce/index.js:17:9)
at processTicksAndRejections (internal/process/task_queues.js:93:5) {
pluginName: '[Function: ]'
}
TypeError: Expected `moduleId` to be of type `string`, got `object`
at resolveFrom (/<path-to-project>/node_modules/resolve-from/index.js:11:9)
at module.exports (/<path-to-project>/node_modules/resolve-from/index.js:34:41)
at module.exports (/<path-to-project>/node_modules/semantic-release-plugin-decorators/node_modules/import-from/index.js:4:49)
at requirePlugin (/<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:4:33)
at resolvePluginFn (/<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:18:18)
at /<path-to-project>/node_modules/semantic-release-plugin-decorators/src/index.js:26:20
at validator (/<path-to-project>/node_modules/semantic-release/lib/plugins/normalize.js:34:30)
at /<path-to-project>/node_modules/semantic-release/lib/plugins/pipeline.js:37:40
at next (/<path-to-project>/node_modules/p-reduce/index.js:17:9)
at processTicksAndRejections (internal/process/task_queues.js:93:5) {
pluginName: '[Function: ]'
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
Exit code: 1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Failed step "analyzeCommits" - TypeError: cb is not a function
Hi, I'm trying execute lerna exec --concurrency 1 -- npx --no-install semantic-release -e semantic-release-monorepo --verify-conditions ...
Read more >Failed step "fail" of plugin "@semantic-release/github" - Stack ...
Default config assumes branch master , so if you're using main you'll get that ERELEASEBRANCHES error. You can try setting the .releaserc.js ...
Read more >semantic-release/semantic-release - Gitter
Hey guys, if I use the @next build I'm not able to use plugins anymore. Is this a known issue? An error occurred...
Read more >semantic-release _may_not be working for our terraform ...
The publish step in our pipelines upon MR merge may not be working. ... PM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin...
Read more >Plugins - Semantic Release - GitBook
If multiple plugins with a analyzeCommits step are defined, the release type will be the highest one ... Responsible for notifying of a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@gmlnchv @JordanForeman @codeandcats Hey y’all, I’ve got an open PR to fix this issue. I’ve mentioned @pmowrer on it, but additional eyes may help get it merged in. 🎉
The new version works for me! Just started using the tool and loving it. Thanks!