semantic-release 15.9.x -> 15.10.x seem to be breaking this plugin
See original GitHub issueI’ll try to take a look myself time permitting, but wanted to let you know. Logs attached:
$ lerna exec --concurrency 1 -- semantic-release -e semantic-release-monorepo
lerna notice cli v3.4.3
lerna info versioning independent
lerna info Executing command in 1 package: "semantic-release -e semantic-release-monorepo"
[3:08:28 AM] [semantic-release] › ℹ Running semantic-release version 15.10.3
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/changelog"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/npm"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "prepare" from "@semantic-release/git"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/npm"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "publish" from "@semantic-release/github"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "success" from "@semantic-release/github"
[3:08:28 AM] [semantic-release] › ✔ Loaded plugin "fail" from "@semantic-release/github"
[3:08:28 AM] [semantic-release] › ✔ Run automated release from branch master
[3:08:30 AM] [semantic-release] › ✔ Allowed to push to the Git repository
[3:08:31 AM] [semantic-release] › ℹ Found git tag @microfleet/core-v13.0.2 associated with version 13.0.2
[3:08:31 AM] [semantic-release] › ℹ Found 9 commits since last release
[3:08:31 AM] [semantic-release] › ℹ Start step "analyzeCommits" of plugin "[Function: ]"
[3:08:31 AM] [semantic-release] › ✖ Failed step "analyzeCommits" of plugin "[Function: ]"
[3:08:31 AM] [semantic-release] › ✖ An error occurred while running semantic-release: { TypeError: Expected `moduleId` to be of type `string`, got `object`
at resolveFrom (/home/runner/core/node_modules/import-from/node_modules/resolve-from/index.js:11:9)
at module.exports (/home/runner/core/node_modules/import-from/node_modules/resolve-from/index.js:34:41)
at module.exports (/home/runner/core/node_modules/import-from/index.js:4:49)
at requirePlugin (/home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:4:33)
at resolvePluginFn (/home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:18:18)
at /home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:26:20
at validator (/home/runner/core/node_modules/semantic-release/lib/plugins/normalize.js:30:28)
at pReduce (/home/runner/core/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
at Promise.all.then.value (/home/runner/core/node_modules/p-reduce/index.js:16:10)
at process._tickCallback (internal/process/next_tick.js:68:7) pluginName: '[Function: ]' }
{ TypeError: Expected `moduleId` to be of type `string`, got `object`
at resolveFrom (/home/runner/core/node_modules/import-from/node_modules/resolve-from/index.js:11:9)
at module.exports (/home/runner/core/node_modules/import-from/node_modules/resolve-from/index.js:34:41)
at module.exports (/home/runner/core/node_modules/import-from/index.js:4:49)
at requirePlugin (/home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:4:33)
at resolvePluginFn (/home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:18:18)
at /home/runner/core/node_modules/semantic-release-plugin-decorators/src/index.js:26:20
at validator (/home/runner/core/node_modules/semantic-release/lib/plugins/normalize.js:30:28)
at pReduce (/home/runner/core/node_modules/semantic-release/lib/plugins/pipeline.js:37:40)
at Promise.all.then.value (/home/runner/core/node_modules/p-reduce/index.js:16:10)
at process._tickCallback (internal/process/next_tick.js:68:7) pluginName: '[Function: ]' }lerna ERR! semantic-release -e semantic-release-monorepo exited 1 in '@microfleet/core'
lerna ERR! semantic-release -e semantic-release-monorepo exited 1 in '@microfleet/core'
Issue Analytics
- State:
- Created 5 years ago
- Reactions:7
- Comments:10 (4 by maintainers)
Top Results From Across the Web
semantic-release 15.9.x -> 15.10.x seem to be breaking this ...
Successfully merging a pull request may close this issue. fix: properly handle modules that are in an array sanpoChew/semantic-release-plugin- ...
Read more >Automating Versioning and Releases Using Semantic Release
Semantic Versioning · MAJOR version is incremented when you make any breaking change · MINOR version is incremented when you add a new...
Read more >@semantic-release/commit-analyzer | Yarn - Package Manager
the commits that contains BREAKING CHANGE or BREAKING CHANGES in their body will be considered breaking changes. the commits with a 'docs' type...
Read more >github [Semantic - release - Gitter
you should also set the git and github plugins to the verifyConditions ... the last X lines of console output. Pierre Vanduynslager.
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
@pmowrer I’m pretty sure this fixes it: https://github.com/Updater/semantic-release-plugin-decorators/pull/9 we are using it fine now
Looks like the entire plugin format changed… I’ll need to sit-down and work out what needs to be updated to support this.
Because
semantic-release
doesn’t provide a necessary plugin hook to make it work with a monorepo, this library has to monkey-patchsemantic-release
through its plugin system. Unfortunately, that makes this library very brittle…