tag:help.appveyor.com,2012-11-13:/discussions/questions/1088-bump-minor-version-after-release-buildAppVeyor: Discussion 2018-10-19T08:17:05Ztag:help.appveyor.com,2012-11-13:Comment/362858992015-03-16T06:16:26Z2015-03-16T06:16:26ZBump minor version after release build<div><p>I'd go with PowerShell approach. Also, you can check this
article about how to push to git during the build: <a href=
"http://www.appveyor.com/docs/how-to/git-push">http://www.appveyor.com/docs/how-to/git-push</a></p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/362858992015-03-17T07:05:24Z2015-03-17T07:05:24ZBump minor version after release build<div><p>Jeavon,</p>
<p>As a suggestion, you might want to think about using a tool like
GitVersion, which can calculate your current version number, based
on the state of your repository:</p>
<p><a href=
"https://github.com/Particularlabs/gitversion">https://github.com/Particularlabs/gitversion</a></p>
<p>This uses git tags to control the "next" release number, and
there are techniques for bumping the version number based on commit
messages.</p>
<p>This means that the "state" of your repository directly controls
the version number, so you don't have to worry about maintaining
that in a separate file. I am now using GitVersion on two OSS
projects, as well as internally.</p>
<p>Gary</p></div>gep13