@@ -46,13 +46,13 @@ assembly-file-versioning-scheme: MajorMinorPatch
46
46
assembly-informational-format : ' {InformationalVersion}'
47
47
mode : ContinuousDelivery
48
48
increment : Inherit
49
- continuous-delivery-fallback-tag : ci
50
- tag -prefix : ' [vV]'
49
+ continuous-delivery-fallback-label : ci
50
+ label -prefix : ' [vV]'
51
51
major-version-bump-message : ' \+semver:\s?(breaking|major)'
52
52
minor-version-bump-message : ' \+semver:\s?(feature|minor)'
53
53
patch-version-bump-message : ' \+semver:\s?(fix|patch)'
54
54
no-bump-message : ' \+semver:\s?(none|skip)'
55
- tag -pre-release-weight : 60000
55
+ label -pre-release-weight : 60000
56
56
commit-message-incrementing : Enabled
57
57
ignore :
58
58
sha : []
@@ -142,26 +142,26 @@ for [increment](#increment),
142
142
[prevent-increment-of-merged-branch-version](#prevent-increment-of-merged-branch-version)
143
143
and [tracks-release-branches](#tracks-release-branches).
144
144
145
- # ## continuous-delivery-fallback-tag
145
+ # ## continuous-delivery-fallback-label
146
146
147
147
When using `mode : ContinuousDeployment`, the value specified in
148
- ` continuous-delivery-fallback-tag ` will be used as the pre-release tag for
148
+ ` continuous-delivery-fallback-label ` will be used as the pre-release label for
149
149
branches which do not have one specified. Default set to `ci`.
150
150
151
151
Just to clarify : For a build name without `...-ci-<buildnumber>` or in other
152
152
words without a `PreReleaseTag` (ergo `"PreReleaseTag":""` in GitVersion's JSON output)
153
- at the end you would need to set `continuous-delivery-fallback-tag ` to an empty
153
+ at the end you would need to set `continuous-delivery-fallback-label ` to an empty
154
154
string (`''`) :
155
155
156
156
` ` ` yaml
157
157
mode: ContinuousDeployment
158
- continuous-delivery-fallback-tag : ''
158
+ continuous-delivery-fallback-label : ''
159
159
...
160
160
` ` `
161
161
162
162
Doing so can be helpful if you use your `main` branch as a `release` branch.
163
163
164
- # ## tag -prefix
164
+ # ## label -prefix
165
165
166
166
A regex which is used to trim Git tags before processing (e.g., v1.0.0). Default
167
167
is `[vV]`, although this is just for illustrative purposes as we do a IgnoreCase
@@ -194,7 +194,7 @@ none` and `+semver: skip`
194
194
When a commit matches **both** the `no-bump-message` **and** any combination of
195
195
the `version-bump-message`, `no-bump-message` takes precedence and no increment is applied.
196
196
197
- # ## tag -pre-release-weight
197
+ # ## label -pre-release-weight
198
198
199
199
The pre-release weight in case of tagged commits. If the value is not set in the
200
200
configuration, a default weight of 60000 is used instead. If the
@@ -293,7 +293,7 @@ branches:
293
293
main:
294
294
regex: ^master$|^main$
295
295
mode: ContinuousDelivery
296
- tag : ''
296
+ label : ''
297
297
increment: Patch
298
298
prevent-increment-of-merged-branch-version: true
299
299
track-merge-target: false
@@ -305,7 +305,7 @@ branches:
305
305
develop:
306
306
regex: ^dev(elop)?(ment)?$
307
307
mode: ContinuousDeployment
308
- tag : alpha
308
+ label : alpha
309
309
increment: Minor
310
310
prevent-increment-of-merged-branch-version: false
311
311
track-merge-target: true
@@ -317,7 +317,7 @@ branches:
317
317
release:
318
318
regex: ^releases?[/-]
319
319
mode: ContinuousDelivery
320
- tag : beta
320
+ label : beta
321
321
increment: None
322
322
prevent-increment-of-merged-branch-version: true
323
323
track-merge-target: false
@@ -329,29 +329,29 @@ branches:
329
329
feature:
330
330
regex: ^features?[/-]
331
331
mode: ContinuousDelivery
332
- tag : '{BranchName}'
332
+ label : '{BranchName}'
333
333
increment: Inherit
334
334
source-branches: [ 'develop', 'main', 'release', 'feature', 'support', 'hotfix' ]
335
- pre-release-weight: 30000
335
+ pre-release-weight: 30000
336
336
pull-request:
337
337
regex: ^(pull|pull\- requests|pr)[/-]
338
338
mode: ContinuousDelivery
339
- tag : PullRequest
339
+ label : PullRequest
340
340
increment: Inherit
341
- tag -number-pattern: '[/-](?<number>\d +)[-/]'
341
+ label -number-pattern: '[/-](?<number>\d +)[-/]'
342
342
source-branches: [ 'develop', 'main', 'release', 'feature', 'support', 'hotfix' ]
343
343
pre-release-weight: 30000
344
344
hotfix:
345
345
regex: ^hotfix(es)?[/-]
346
346
mode: ContinuousDelivery
347
- tag : beta
347
+ label : beta
348
348
increment: Inherit
349
349
source-branches: [ 'release', 'main', 'support', 'hotfix' ]
350
350
pre-release-weight: 30000
351
351
support:
352
352
regex: ^support[/-]
353
353
mode: ContinuousDelivery
354
- tag : ''
354
+ label : ''
355
355
increment: Patch
356
356
prevent-increment-of-merged-branch-version: true
357
357
track-merge-target: false
@@ -457,15 +457,15 @@ The header for all the individual branch configuration.
457
457
458
458
Same as for the [global configuration, explained above](#mode).
459
459
460
- # ## tag
460
+ # ## label
461
461
462
- The pre release tag to use for this branch. Use the value `useBranchName` to use
462
+ The pre release label to use for this branch. Use the value `useBranchName` to use
463
463
the branch name instead. For example `feature/foo` would become a pre-release
464
- tag of `foo` with this value. Use the value `{BranchName}` as a placeholder to
465
- insert the branch name. For example `feature/foo` would become a pre-release tag
464
+ label of `foo` with this value. Use the value `{BranchName}` as a placeholder to
465
+ insert the branch name. For example `feature/foo` would become a pre-release label
466
466
of `alpha.foo` with the value of `alpha.{BranchName}`.
467
467
468
- **Note:** To clear a default use an empty string: `tag : ''`
468
+ **Note:** To clear a default use an empty string: `label : ''`
469
469
470
470
# ## increment
471
471
@@ -482,15 +482,15 @@ In a GitFlow-based repository, setting this option can have implications on the
482
482
better version source proposed by the `MergeMessageBaseVersionStrategy`. For
483
483
more details and an in-depth analysis, please see [the discussion][2506].
484
484
485
- # ## tag -number-pattern
485
+ # ## label -number-pattern
486
486
487
487
Pull requests require us to extract the pre-release number out of the branch
488
488
name so `refs/pulls/534/merge` builds as `PullRequest.534`. This is a regex with
489
489
a named capture group called `number`.
490
490
491
491
If the branch `mode` is set to `ContinuousDeployment`, then the extracted
492
- ` number` is appended to the name of the pre-release tag and the number portion
493
- is the number of commits since the last tag . This enables consecutive commits to
492
+ ` number` is appended to the name of the pre-release label and the number portion
493
+ is the number of commits since the last label . This enables consecutive commits to
494
494
the pull request branch to generate unique full semantic version numbers when
495
495
the branch is configured to use ContinuousDeployment mode.
496
496
@@ -500,10 +500,10 @@ the branch is configured to use ContinuousDeployment mode.
500
500
branches:
501
501
pull-request:
502
502
mode: ContinuousDeployment
503
- tag : PullRequest
503
+ label : PullRequest
504
504
increment: Inherit
505
505
track-merge-target: true
506
- tag -number-pattern: '[/-](?<number>\d +)[-/]'
506
+ label -number-pattern: '[/-](?<number>\d +)[-/]'
507
507
` ` `
508
508
509
509
# ## track-merge-target
0 commit comments