Skip to content
This repository has been archived by the owner on Dec 27, 2023. It is now read-only.

Create a release branch #136

Open
baruchiro opened this issue Sep 29, 2021 · 0 comments
Open

Create a release branch #136

baruchiro opened this issue Sep 29, 2021 · 0 comments

Comments

@baruchiro
Copy link
Owner

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant