With the current implementation of SemanticRelease (documented here), to publish a version with multiple recorded changes (like a new feature and dependencies upgrades), you have to develop those two in the same PR.
This is because the SemanticRelease pipeline is triggered when pushing to master.
We need to trigger it in another way, maybe by triggering it on another branch, maybe manual, any idea is welcome.
With the current implementation of SemanticRelease (documented here), to publish a version with multiple recorded changes (like a new feature and dependencies upgrades), you have to develop those two in the same PR.
This is because the SemanticRelease pipeline is triggered when pushing to
master.We need to trigger it in another way, maybe by triggering it on another branch, maybe manual, any idea is welcome.