Replies: 1 comment 1 reply
-
We do not recommend using semantic-release for a gitflow style workflow, but merging your production branch back into main should accomplish the versioning that you are targeting |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey! I realise this might be a workflow question, but wanted to ask how to achieve the following.
We have a
main
branch which gets deployed to staging environment, and then we merge it intoproduction
branch to go live.semantic-release
will create a release candidate onmain
, and actual release onproduction
.The problem I have is this. Let's say we're starting with version 1.0.0.
main
, create releasev1.0.1-rc.1
(good)main
branch intoproduction
, create releasev1.0.1
(good)main
, create releasev1.0.1-rc.2
(uh oh!)I understand why this happens.
semantic-release
bumpspackage.json
onmain
tov1.0.1-rc.1
, and when we deploy to production it bumps it tov1.0.1
, but only on theproduction
branch.My question is, how to fix this so that when we release,
semantic-release
would bump the version in step 3 above tov1.0.2-rc.1
?Beta Was this translation helpful? Give feedback.
All reactions