-
|
Hi, I have following use case and would like to ask what would be the best way to do it using I have a project, lets just call it
To achieve this I will need to have separate branches for both versions, let's say: Is this the recommended approach? I remember that I faced some issues in the past when I did this (don't remember the errors though). However I just tried it in a fresh workspace and it seemed to work without any issues |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 5 replies
-
|
Did you find an answer to your question? I have a similar situation for my ngx-jodit project. I plan to use semver for different branches with two projects for each branch and different Angular 16 compatibility |
Beta Was this translation helpful? Give feedback.
-
|
Hi @julianpoemp I did release multiple major minor and path versions switching the branches in between. I did not face any issue :) I hope this helps. If you want I can also share this repository with you. I should still have it (somewhere 😅) on my computer. |
Beta Was this translation helpful? Give feedback.
-
|
that would be awesome! |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I also released a project from different branches and it works fine. I think that there's only one detail to mention, the |
Beta Was this translation helpful? Give feedback.
-
Here you go: https://github.com/mikelgo/semver-multi-branch-versioning |
Beta Was this translation helpful? Give feedback.
-
|
thank you! |
Beta Was this translation helpful? Give feedback.
-
|
You're welcome. I hope it helps |
Beta Was this translation helpful? Give feedback.
Here you go: https://github.com/mikelgo/semver-multi-branch-versioning
Note: it is just a minimal version. I e.g. did not cherry pick commits from v1.x.x branch to the main branch (reflects the current version). You might want to this, e.g. when you need to bugfix something in multiple versions.