-
Hi With v5 we had a pull-request:
mode: ContinuousDeployment
regex: ((pull|pull\-requests|pr)[/-]|[/-](merge))
tag: pr
tag-number-pattern: '[/-]?(?<number>\d+)'
prevent-increment-of-merged-branch-version: false To be clear: we have a small routine in our build that generates this version like: This produces the following version (e.g. from build pipeline output):
So, the version generated by gitversion was 6.13.0-pr.2733 With v6 we now have the following issue: First, fix the yaml for v6 to pull-request:
mode: ContinuousDeployment
regex: ((pull|pull\-requests|pr)[/-]|[/-](merge))
label: pr
label-number-pattern: '[/-]?(?<number>\d+)'
prevent-increment:
of-merged-branch: false Now, the version generated from
SemVer should be: So, there is no I'm pretty sure this is a misconfiguration, but cannot find it. Help is really appreciated. Thank you |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
You need to keep in mind that the latest git version update was a major version update. Thus just to copy the configuration one by one and migrate it is not the right way without understanding what have changed. Like mentioned in the breaking change documentation (see Link[1]):
Please try the following configuration (see Link[2]): workflow: GitFlow/v1 or (see Link[3]) workflow: GitHubFlow/v1 Link[1]: https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md |
Beta Was this translation helpful? Give feedback.
You need to keep in mind that the latest git version update was a major version update. Thus just to copy the configuration one by one and migrate it is not the right way without understanding what have changed.
Like mentioned in the breaking change documentation (see Link[1]):
Please try the following configuration (see Link[2]):
or (see Link[3])
Link[1]: https://github.com/GitTools/GitVersion/blob/main/BREAKING_CHANGES.md
Lin…