Downloads of v 2.0.1:


Last Update:

20 Jan 2015

Package Maintainer(s):

Software Author(s):

  • NServiceBus Ltd


Git, Versioning, GitVersion, GitFlowVersion, GitFlow, GitHubFlow, SemVer


This is not the latest version of GitVersion available.

  • 1
  • 2
  • 3

2.0.1 | Updated: 20 Jan 2015



Downloads of v 2.0.1:



Software Author(s):

  • NServiceBus Ltd

  • 1
  • 2
  • 3
GitVersion 2.0.1

This is not the latest version of GitVersion available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Unknown

Verification Testing Unknown

Scan Testing Successful:

No detections found in any package files


To install GitVersion, run the following command from the command line or from PowerShell:


To upgrade GitVersion, run the following command from the command line or from PowerShell:


To uninstall GitVersion, run the following command from the command line or from PowerShell:


NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade gitversion.portable -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade gitversion.portable -y --source="'STEP 3 URL'"

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Ensure gitversion.portable installed
    name: gitversion.portable
    state: present
    version: 2.0.1
    source: STEP 3 URL

See docs at

chocolatey_package 'gitversion.portable' do
  action    :install
  version  '2.0.1'
  source   'STEP 3 URL'

See docs at

    Name: gitversion.portable,
    Version: 2.0.1,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller gitversion.portable
   Name     = 'gitversion.portable'
   Ensure   = 'Present'
   Version  = '2.0.1'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'gitversion.portable':
  provider => 'chocolatey',
  ensure   => '2.0.1',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install gitversion.portable version="2.0.1" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

There are versions of this package awaiting moderation . See the Version History section below.

This package was approved as a trusted package on 20 Jan 2015.


Derives SemVer information from a repository following GitFlow or GitHubFlow.

Generate-BinFile "gfv" "$packageFolder\Tools\GitVersion.exe"
Write-ChocolateySuccess "GitVersion"
Remove-BinFile "gfv" "$packageFolder\Tools\GitVersion.exe"
Remove-BinFile "GitVersion" "$packageFolder\Tools\GitVersion.exe"
Write-ChocolateySuccess "GitVersion"

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
GitVersion 5.6.11 2957 Monday, July 26, 2021 Approved
GitVersion 5.6.10 6773 Thursday, May 27, 2021 Approved
GitVersion 5.6.9 3588 Thursday, April 29, 2021 Approved
GitVersion 5.6.8 2633 Tuesday, April 6, 2021 Approved
GitVersion 5.6.7 629 Thursday, March 25, 2021 Approved
GitVersion 5.6.6 5610 Wednesday, February 10, 2021 Approved
GitVersion 5.6.5 611 Sunday, February 7, 2021 Approved
GitVersion 5.6.4 2630 Tuesday, January 19, 2021 Approved
GitVersion 5.6.3 2130 Friday, January 8, 2021 Approved

This package has no dependencies.

Discussion for the GitVersion Package

Ground Rules:

  • This discussion is only about GitVersion and the GitVersion package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or GitVersion, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus