Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
arkadioz opened this issue Feb 13, 2024 · 0 comments
Open

Comments

@arkadioz
Copy link

arkadioz commented Feb 13, 2024

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?

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

No branches or pull requests

1 participant