Automatic Versioning Based on Branch Names Using Semantic-Release Package #3050
Replies: 1 comment
-
no, this is not possible. if that is your goal, semantic-release is not the tool you are looking for |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I am currently exploring the capabilities of the semantic-release package and wondering if it is possible to update versioning based on branch names instead of commit messages. Specifically, I have a 'next' branch that serves as a release candidate. Whenever I merge a feature into it, the branch name always starts with 'feature/'. My goal is to automatically update the minor versioning when features are merged into 'next', and similarly, update patch versioning for branches starting with 'bugfix/'.
To provide a clear scenario:
I have extensively searched the documentation and online resources but haven't found a clear solution for this specific use case. I would appreciate any insights or suggestions on how to achieve this versioning strategy with semantic-release.
I have tried the following configurations already which did not meet my requirements:
And
Both of them gave me a ERELEASEBRANCHES error with the message being "A minimum of 1 and a maximum of 3 release branches are required in the branches configuration.".
Beta Was this translation helpful? Give feedback.
All reactions