search

dhoulb / multi-semantic-release

Proof of concept that wraps semantic-release to work with monorepos.
BSD Zero Clause License
200 stars 37 forks source link

question: can MSR define plugin's default options ? #110

Open Badisi opened 2 years ago

Badisi commented 2 years ago

When using the plugin @semantic-release/github, the following comment is added to any issues or PRs that relates to the release:

🎉 This PR is included in version 2.0.0-beta.11 🎉

The release is available on [npm package (@beta dist-tag)]()

Your semantic-release bot 📦🚀

But when releasing multiple packages it is obvious that the version here (ie. 2.0.0-beta.11) does not really help.

One could use the plugin's successComment option to change the comment and maybe use something like nextRelease.gitTag instead of nextRelease.version (see get-success-comment.js#L7).

But I was wondering if MSR could set that by default ? and how ? as I'm not familiar with how SR/MSR lifecycle hooks are working.

Thanks!