You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: