1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
|
.TH DUNAMAI "1" "2024\-08\-07" "dunamai 1.22.0" "Dunamai"
.SH NAME
dunamai
.SH SYNOPSIS
.B dunamai
[-h] {from,check} ...
.SH DESCRIPTION
Generate dynamic versions
.SH
POSITIONAL ARGUMENTS
.SS \fBdunamai from\fR
Generate version from a particular VCS
usage: dunamai from [\-h]
{any,git,mercurial,darcs,subversion,bazaar,fossil,pijul}
...
Generate version from a particular VCS
.SS \fBdunamai from any\fR
Generate version from any detected VCS
usage: dunamai from any [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-ignore\-untracked] [\-\-tagged\-metadata]
[\-\-pattern PATTERN] [\-\-pattern\-prefix PATTERN_PREFIX]
[\-\-format FORMAT] [\-\-style {pep440,semver,pvp}]
[\-\-latest\-tag] [\-\-strict] [\-\-path PATH] [\-\-debug]
[\-\-bump] [\-\-full\-commit]
[\-\-commit\-length COMMIT_LENGTH]
[\-\-tag\-branch TAG_BRANCH] [\-\-tag\-dir TAG_DIR]
Generate version from any detected VCS
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-ignore\-untracked\fR
Ignore untracked files when determining whether the repository is dirty (only:
Git)
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-full\-commit\fR
Get the full commit hash instead of the short form (only: Git, Mercurial)
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.TP
\fB\-\-tag\-branch\fR \fI\,TAG_BRANCH\/\fR
Branch on which to find tags, if different than the current branch (only: Git)
.TP
\fB\-\-tag\-dir\fR \fI\,TAG_DIR\/\fR
Location of tags relative to the root (only: Subversion)
.RE
.SS \fBdunamai from git\fR
Generate version from Git
usage: dunamai from git [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-ignore\-untracked] [\-\-tagged\-metadata]
[\-\-pattern PATTERN] [\-\-pattern\-prefix PATTERN_PREFIX]
[\-\-format FORMAT] [\-\-style {pep440,semver,pvp}]
[\-\-latest\-tag] [\-\-strict] [\-\-path PATH] [\-\-debug]
[\-\-bump] [\-\-full\-commit]
[\-\-commit\-length COMMIT_LENGTH]
[\-\-tag\-branch TAG_BRANCH]
Generate version from Git
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-ignore\-untracked\fR
Ignore untracked files when determining whether the repository is dirty (only:
Git)
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-full\-commit\fR
Get the full commit hash instead of the short form (only: Git, Mercurial)
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.TP
\fB\-\-tag\-branch\fR \fI\,TAG_BRANCH\/\fR
Branch on which to find tags, if different than the current branch (only: Git)
.RE
.SS \fBdunamai from mercurial\fR
Generate version from Mercurial
usage: dunamai from mercurial [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX]
[\-\-format FORMAT] [\-\-style {pep440,semver,pvp}]
[\-\-latest\-tag] [\-\-strict] [\-\-path PATH]
[\-\-debug] [\-\-bump] [\-\-full\-commit]
[\-\-commit\-length COMMIT_LENGTH]
Generate version from Mercurial
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-full\-commit\fR
Get the full commit hash instead of the short form (only: Git, Mercurial)
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.RE
.SS \fBdunamai from darcs\fR
Generate version from Darcs
usage: dunamai from darcs [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX] [\-\-format FORMAT]
[\-\-style {pep440,semver,pvp}] [\-\-latest\-tag]
[\-\-strict] [\-\-path PATH] [\-\-debug] [\-\-bump]
[\-\-commit\-length COMMIT_LENGTH]
Generate version from Darcs
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.RE
.SS \fBdunamai from subversion\fR
Generate version from Subversion
usage: dunamai from subversion [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX]
[\-\-format FORMAT] [\-\-style {pep440,semver,pvp}]
[\-\-latest\-tag] [\-\-strict] [\-\-path PATH]
[\-\-debug] [\-\-bump]
[\-\-commit\-length COMMIT_LENGTH]
[\-\-tag\-dir TAG_DIR]
Generate version from Subversion
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.TP
\fB\-\-tag\-dir\fR \fI\,TAG_DIR\/\fR
Location of tags relative to the root (only: Subversion)
.RE
.SS \fBdunamai from bazaar\fR
Generate version from Bazaar
usage: dunamai from bazaar [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX] [\-\-format FORMAT]
[\-\-style {pep440,semver,pvp}] [\-\-latest\-tag]
[\-\-strict] [\-\-path PATH] [\-\-debug] [\-\-bump]
[\-\-commit\-length COMMIT_LENGTH]
Generate version from Bazaar
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.RE
.SS \fBdunamai from fossil\fR
Generate version from Fossil
usage: dunamai from fossil [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX] [\-\-format FORMAT]
[\-\-style {pep440,semver,pvp}] [\-\-latest\-tag]
[\-\-strict] [\-\-path PATH] [\-\-debug] [\-\-bump]
[\-\-commit\-length COMMIT_LENGTH]
Generate version from Fossil
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.RE
.SS \fBdunamai from pijul\fR
Generate version from Pijul
usage: dunamai from pijul [\-h] [\-\-metadata] [\-\-no\-metadata] [\-\-dirty]
[\-\-tagged\-metadata] [\-\-pattern PATTERN]
[\-\-pattern\-prefix PATTERN_PREFIX] [\-\-format FORMAT]
[\-\-style {pep440,semver,pvp}] [\-\-latest\-tag]
[\-\-strict] [\-\-path PATH] [\-\-debug] [\-\-bump]
[\-\-commit\-length COMMIT_LENGTH]
Generate version from Pijul
options:
.RS 7
.TP
\fB\-\-metadata\fR
Always include metadata. Ignored when \-\-format is used
.TP
\fB\-\-no\-metadata\fR
Never include metadata. Ignored when \-\-format is used
.TP
\fB\-\-dirty\fR
Include dirty flag if applicable. Ignored when \-\-format is used
.TP
\fB\-\-tagged\-metadata\fR
Include tagged metadata if applicable. Ignored when \-\-format is used
.TP
\fB\-\-pattern\fR \fI\,PATTERN\/\fR
Regular expression matched against the version source. This must contain one
capture group named `base` corresponding to the release segment of the source.
Optionally, it may contain another two groups named `stage` and `revision`
corresponding to a prerelease type (such as 'alpha' or 'rc') and number (such
as in 'alpha\-2' or 'rc3'). It may also contain a group named `tagged_metadata`
corresponding to extra metadata after the main part of the version (typically
after a plus sign). There may also be a group named `epoch` for the PEP 440
concept. If the `base` group is not present, then instead this will be
interpreted as a named preset, which may be one of the following: `default`,
`default\-unprefixed`
.TP
\fB\-\-pattern\-prefix\fR \fI\,PATTERN_PREFIX\/\fR
Insert this after the pattern's start anchor (`^`).
.TP
\fB\-\-format\fR \fI\,FORMAT\/\fR
Custom output format. Available substitutions: {base}, {stage}, {revision},
{distance}, {commit}, {dirty}, {tagged_metadata}, {epoch}, {branch},
{branch_escaped}, {timestamp}
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Preconfigured output format. Will default to PEP 440 if not set and no custom
format given. If you specify both a style and a custom format, then the format
will be validated against the style's rules
.TP
\fB\-\-latest\-tag\fR
Only inspect the latest tag on the latest tagged commit for a pattern match
.TP
\fB\-\-strict\fR
Elevate warnings to errors. When there are no tags, fail instead of falling
back to 0.0.0
.TP
\fB\-\-path\fR \fI\,PATH\/\fR
Directory to inspect, if not the current working directory
.TP
\fB\-\-debug\fR
Display additional information on stderr for troubleshooting
.TP
\fB\-\-bump\fR
Increment the last part of the version `base` by 1, unless the `stage` is set,
in which case increment the `revision` by 1 or set it to a default of 2 if
there was no `revision` Does nothing when on a commit with a version tag.
.TP
\fB\-\-commit\-length\fR \fI\,COMMIT_LENGTH\/\fR
Use this many characters from the start of the full commit hash
.RE
.SS \fBdunamai check\fR
Check if a version is valid for a style
usage: dunamai check [\-h] [\-\-style {pep440,semver,pvp}] [version]
Check if a version is valid for a style
arguments:
.RS 7
.TP
\fBversion\fR
Version to check; may be piped in
.RE
options:
.RS 7
.TP
\fB\-\-style\fR \fI\,{pep440,semver,pvp}\/\fR
Style against which to check
.RE
.SH AUTHOR
.nf
'Matthew T. Kennerly (mtkennerly)'
.fi
.SH DISTRIBUTION
The latest version of dunamai may be downloaded from
.UR https://github.com/mtkennerly/dunamai
.UE
|
