commit-analyzer icon indicating copy to clipboard operation
commit-analyzer copied to clipboard

Question: after merging from a prerelease branch into a release branch

Open arkadioz opened this issue 1 year ago • 0 comments

Hello, I am doing some tests when merging a prerelease branch for example develop into a release branch for example main, I was expecting that after the release of a new tag happens from main, I do not need to merge main into develop for it to "sync" with the new latest tag, but right now if after releasing a new latest tag from main, I keep adding new features into develop and run semantic release it will keep generating prerelease tag with the version before. For example:

If I have the prerelease version 18.1.1-develop.1, then I merge to main it successfully generates the version 18.1.1, but after this, if I do not merge main into develop, and do a new patch in develop, develop will generate tag 18.1.1-develop.2, but I expect 18.1.2-develop.1, to get 18.1.2-develop.1 I have to merge main into develop before adding any new changes, but I would like to avoid this in order to have a more linear git history, is it possible with some kind of configuration? Maybe I have to set both branches channel to latest or how could I do it?

arkadioz avatar Feb 13 '24 17:02 arkadioz