1Dist::Zilla::Plugin::GiUts:e:rNeCxotnVterrisbiuotne(d3D)Piesrtl::DZoiclulmae:n:tPaltuigoinn::Git::NextVersion(3)
2
3
4
6 Dist::Zilla::Plugin::Git::NextVersion - Provide a version number by
7 bumping the last git release tag
8
10 version 2.048
11
13 In your dist.ini:
14
15 [Git::NextVersion]
16 first_version = 0.001 ; this is the default
17 version_by_branch = 0 ; this is the default
18 version_regexp = ^v(.+)$ ; this is the default
19
21 This does the VersionProvider role. It finds the last version number
22 from your Git tags, increments it using Version::Next, and uses the
23 result as the "version" parameter for your distribution.
24
25 In addition, when making a release, it ensures that the version being
26 released has not already been tagged. (The Git::Tag plugin has a
27 similar check, but Git::Tag only checks for an exact match on the tag.
28 Since Git::NextVersion knows how to extract version numbers from tags,
29 it can find duplicates that Git::Tag would miss.)
30
31 The plugin accepts the following options:
32
33 • "first_version" - if the repository has no tags at all, this
34 version is used as the first version for the distribution. It
35 defaults to "0.001".
36
37 • "version_by_branch" - if true, consider only tags on the current
38 branch when looking for the previous version. If you have a
39 maintenance branch for stable releases and a development branch for
40 trial releases, you should set this to 1. (You'll also need git
41 version 1.6.1 or later.) The default is to look at all tags,
42 because finding the tags reachable from a branch is a more
43 expensive operation than simply listing all tags.
44
45 • "version_regexp" - regular expression that matches a tag containing
46 a version. It must capture the version into $1. Defaults to
47 ^v(.+)$ which matches the default "tag_format" from the Git::Tag
48 plugin. If you change "tag_format", you must set a corresponding
49 "version_regexp".
50
51 You can also set the "V" environment variable to override the new
52 version. This is useful if you need to bump to a specific version.
53 For example, if the last tag is 0.005 and you want to jump to 1.000 you
54 can set V = 1.000.
55
56 $ V=1.000 dzil release
57
58 Because tracing history takes time, if you use the "version_by_branch"
59 option, Git::NextVersion will create a .gitnxtver_cache file in your
60 repository root to track the highest version number that is an ancestor
61 of the HEAD revision. You should add .gitnxtver_cache to your
62 .gitignore file. It will automatically be pruned from the
63 distribution.
64
66 Bugs may be submitted through the RT bug tracker
67 <https://rt.cpan.org/Public/Dist/Display.html?Name=Dist-Zilla-Plugin-
68 Git> (or bug-Dist-Zilla-Plugin-Git@rt.cpan.org <mailto:bug-Dist-Zilla-
69 Plugin-Git@rt.cpan.org>).
70
71 There is also a mailing list available for users of this distribution,
72 at <http://dzil.org/#mailing-list>.
73
74 There is also an irc channel available for users of this distribution,
75 at "#distzilla" on "irc.perl.org" <irc://irc.perl.org/#distzilla>.
76
78 Jerome Quelin
79
81 This software is copyright (c) 2009 by Jerome Quelin.
82
83 This is free software; you can redistribute it and/or modify it under
84 the same terms as the Perl 5 programming language system itself.
85
86
87
88perl v5.36.0 2023-D0i1s-t2:0:Zilla::Plugin::Git::NextVersion(3)