Repository navigation
[Bug] Incrementing patch version automatically on main without tags nor specific commit messages #3570
Description
Discussed in #2660
Originally posted by franknarf8 April 13, 2021
Hello,
I have just upgraded my GitVersion to the latest, but I can't find a way to reproduce the behavior I expect, and used to achieve with the previous GitVersion. (the change appeared between since 5.0.0)
When using Mainline, I would expect that each merge commits to master cause the patch version to increment. (Without any commit messages required)
Using the following GitVersion.yml (I'm generating pip versions here, please disregard the branches) :
mode: Mainline
next-version: 1.0.0
branches:
release:
tag: 'rc'
feature:
regex: ^features?[/-]|^(pull|pull\-requests|pr)[/-]
tag: 'dev'
develop:
tag: 'a'
hotfix:
tag: 'post'
ignore:
sha: []
merge-message-formats: {}
With this dummy git repo :
* 0bac05d 3 minutes ago (HEAD -> master)
|\
| * 2922409 3 minutes ago (feature/first-feature)
| * 2246a3e 7 minutes ago
|/
* bc00c9f 7 minutes ago (tag: 1.2.3)
GitVersion 5.6.8 is inferring : 1.2.3
whereas 5.0.0 inferred : 1.2.4
I would expect 1.2.4 here, how can I achieve this?
Reacted by Hardy Hobeck
Activity
[-]Incrementing `patch` version automatically on `main` without tags nor specific commit messages[/-][+][Bug] Incrementing `patch` version automatically on `main` without tags nor specific commit messages[/+]github-actions commentedon Sep 29, 2023
This issue has been automatically marked as stale because it has not had recent activity. After 30 days from now, it will be closed if no further activity occurs.
arturcic commentedon Mar 9, 2024
🎉 This issue has been resolved in version 6.0.0-beta.6 🎉
The release is available on:
Your GitReleaseManager bot 📦🚀
simbeldev commentedon Apr 22, 2024
Given that this is still in beta... do we have any workaround?