Adds support for versionTemplate, which is designed to be populated with the base branch name.
This means we can use the same settings regardless of the branch, but running against a version branch (e.g. v1.2.x) will now:
fail if the next computed version does not start with1.2.
set defaultBump appropriately (to patch), even if we're using minor for the main branch
It also gives more flexibility, e.g. if you need to cut a release between 1.2.3 and 1.2.4, you can now make a 1.2.3.x branch and it'll start pumping out versions with 4 components just for that branch.
It also supports "next major" branch workflow - e.g. if master is on 4.x.x you can create a v5.x.0 branch which will be ahead of master.
Adds support for versionTemplate, which is designed to be populated with the base branch name.
This means we can use the same settings regardless of the branch, but running against a version branch (e.g.
v1.2.x
) will now:1.2.
patch
), even if we're usingminor
for the main branchIt also gives more flexibility, e.g. if you need to cut a release between
1.2.3
and1.2.4
, you can now make a1.2.3.x
branch and it'll start pumping out versions with 4 components just for that branch.It also supports "next major" branch workflow - e.g. if master is on
4.x.x
you can create av5.x.0
branch which will be ahead of master.