Releases: GitTools/GitVersion
v4.0.0-beta.7
- Bug fix: This release fixes a issue with GitVersion where branch normalisation can move the HEAD which is being built by the build server. This only affects you if the branch you are building moves on between when your build is queued and when the build runs but is a pretty bad bug because you can build something which you didn't think you were building.
- Feature: When using Dynamic repositories, it is not safe to run concurrent builds on the same machine, GitVersion locks dynamic repositories while it is running.
- Breaking: This release also introduces branch config aliases, so rather than putting a regex as the key you can name it, and use the
regexproperty. See docs at branch configuration
Issues:
- #1033 - Upgraded to newer GitTools.Core which fixes normalisation issues contributed by Jake Ginnivan (JakeGinnivan)
- #1032 - Fixed deployment script error contributed by Jake Ginnivan (JakeGinnivan)
- #1029 - Named branch configuration contributed by Jake Ginnivan (JakeGinnivan)
- #995 - Alias branch types in config
v3.6.4
This release fixes a issue with GitVersion where branch normalisation can move the HEAD which is being built by the build server. This only affects you if the branch you are building moves on between when your build is queued and when the build runs but is a pretty bad bug because you can build something which you didn't think you were building.
v3.6.3
v4.0.0-beta.5
- #1006 - Fixing exception when forward merging support branches into master wi… contributed by Jake Ginnivan (JakeGinnivan)
- #1002 - Add NuGetPreReleaseTag variable contributed by Guillaume Rouchon (qetza)
Commits: 2ed1ad7...ae26b81
v4.0.0-beta.4
Getting closer to a stable v4 release
- #1005 - Mainline fixes contributed by Jake Ginnivan (JakeGinnivan)
- #1003 - Add readme to the docs directory contributed by Asbjørn Ulsberg (asbjornu)
- #1001 - On develop startegy, if the develop branch and release merge base are the same version should not be bump
- #1000 - Develop version not bump if no new commit since release branch contributed by Guillaume Rouchon (qetza)
- #998 - Mainline mode support branches
- #991 - Add mainline to gitversion init
Commits: 08f882e...5265fad
v4.0.0-beta.3
This release makes a number of improvements to Mainline mode, including feature branches and pull requests will generate different versions for every commit.
- #997 - Mainline PR improvements contributed by Jake Ginnivan (JakeGinnivan)
- #990 - Update VSTS variable references in the docs contributed by Fredrik Johansson (frenkan)
- #989 - Mode and configuration documentation cleanup contributed by Asbjørn Ulsberg (asbjornu)
- #978 - Version calculation should not use tags from not merged branch contributed by (lerthe61)
- #976 - Improve documentation for commits-before configuration contributed by Pascal Berger (pascalberger)
Commits: 0d2afb9...b48a69c
v4.0.0-beta.2
This release fixes the same issues as v3.6.2 but for the v4 release.
v3.6.2
This version fixes a regression with the cache key calculation in v3.6.0. When using the MSBuild tasks with lots of projects you would see a greatly increased build time because each project would calculate the version multiple times.
Thanks to @tofutim for the fix and @DanielRose @rubenmamo @tpluscode @asbjornu @Martin-Andersen for contributing to the discussions to help get it fixed.
Version is incremented twice if the base version commit also has an explicit semver message was also fixed by #975 (thanks @MikeLarah)
v4.0.0-beta.1
v4 has two major changes, there likely will be a few issues which fall out of these changes hence the beta.
1. Develop tag changed from unstable to alpha
In GitFlow the default tag on develop has changed from unstable to alpha. It also more aggressively bumps, so develop. An example is below (the final tag is missing, check the docs at GitFlow examples for up to date examples
2. Introduced Mainline development mode
One of the current hard requirements for GitVersion is that you tag when you release. This is due to GitVersions predictive nature, you need to communicate back to GitVesion that you have released something which was built, then it will increment.
Mainline mode lets GitVersion imply a release from any merge or commit to master. The version in this initial beta is an initial proof of concept, it doesn't have the test coverage the other modes have. So if you find an issue please submit a pull request with a test demonstrating your issue. That way we can improve this mode and get better test coverage at the same time.
See docs at versioning modes
- #958 - Update documentation to use alpha prefix contributed by Pascal Berger (pascalberger)
- #950 - Mainline development mode contributed by Jake Ginnivan (JakeGinnivan)
- #832 - Bump develop when release branch created contributed by Jake Ginnivan (JakeGinnivan)
- #695 - Increment "develop" version when branching release
Commits: 11d48a7...22e0342
v3.6.1
- #892 - Fixed issues #863 and #870: invalid cache key computation and config file location contributed by Sergio Rykov (sergiorykov)
- #949 - Bunch of build/deployment script fixes contributed by Jake Ginnivan (JakeGinnivan)
- #945 #925 - Fix dead dynamic repositories documentation link contributed by Pascal Berger (pascalberger)
- #944 - Set verbosity to minimal for all build environments contributed by Pascal Berger (pascalberger)
- #943 - Fix tfs task build contributed by Pascal Berger (pascalberger)
Commits: a3c2adf...35c696a