Downloads:

467,838

Downloads of v 5.6.0:

1,432

Last Update:

19 Dec 2020

Package Maintainer(s):

Software Author(s):

  • GitTools and Contributors

Tags:

Git Versioning GitVersion GitFlowVersion GitFlow GitHubFlow SemVer

GitVersion

This is not the latest version of GitVersion available.

  • 1
  • 2
  • 3

5.6.0 | Updated: 19 Dec 2020

Downloads:

467,838

Downloads of v 5.6.0:

1,432

Maintainer(s):

Software Author(s):

  • GitTools and Contributors

  • 1
  • 2
  • 3
GitVersion 5.6.0

This is not the latest version of GitVersion available.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

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 https://community.chocolatey.org/api/v2. 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 https://community.chocolatey.org/api/v2)

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'"
$exitCode = $LASTEXITCODE

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
  win_chocolatey:
    name: gitversion.portable
    state: present
    version: 5.6.0
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


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

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: gitversion.portable,
    Version: 5.6.0,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller gitversion.portable
{
   Name     = 'gitversion.portable'
   Ensure   = 'Present'
   Version  = '5.6.0'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


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

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


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

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

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 19 Dec 2020.

Description

Derives SemVer information from a repository following GitFlow or GitHubFlow.


tools\chocolateyInstall.ps1
Generate-BinFile "gv" "$packageFolder\Tools\GitVersion.exe"
tools\chocolateyUninstall.ps1
Remove-BinFile "gv" "$packageFolder\Tools\GitVersion.exe"
Remove-BinFile "GitVersion" "$packageFolder\Tools\GitVersion.exe"
tools\clrcompression.dll
md5: D492E8E97FA8029E6DBB4DA3F1B00F5A | sha1: 08805F048E5F5D20D09C374CFA21C4D43E715FD3 | sha256: 267F9972F35261D8F333348FB6452CC1D3E8A6A4767CBC5676E341408C653569 | sha512: 1E55A74F227C5484B0F0B7D02BDF6CEFAC9D240745A13D585DAC1595519A196AA5F7A113816526C3BA8ED868E9E5C42474ADAC5939EA46E23EA5D2C566F78C1B
tools\clrjit.dll
md5: 6CCD18717D1E5E1584B3CC6B5F3C5FC2 | sha1: C2AD52ABFA45FEAC6AC61D64203212A05445B875 | sha256: 5E401AE53C02913A75533EC69606CC27F873A35EC29854EC935B0A9358B34F44 | sha512: 559429752EBB3D619C917896D24B6D65890E119537C5E1109EB7E49E87D0F63EFC0EAE4E38CEBEC555D7459B7FDBEAE813A2A30E7FB0F36878BFE352649A2360
tools\coreclr.dll
md5: 08FB56CF2BD907E3BBBABE41E50B8701 | sha1: 3468528D05108F86146462A8390D7B893B881B05 | sha256: 87C11E3039725FF82DC96EF5BCC6F315DFC0366A8DC25DF43685C5F99A2A4ADE | sha512: 9A4F38C6C6CAA4FA75C68AF3D00BFE96D5EC06CA4E8DDA10FD7EC014BB230AAFFC9A6D0FD2FA35D0F039CD81E70CC0A9B25D28FC0DE72B0E31BFC61F0A5C2DF6
tools\git2-6777db8.dll
md5: 7CB3B2DA102EDD5C7219360F008CD76A | sha1: EE28B1EA57FB387412D936705AF4637DA1E6C1B2 | sha256: 0B45919FDEACA4F001455BA8B78B797600449E77CEC99D6479098DED11379881 | sha512: 1F1A2B388EB603E086130C580A86A6910FEEFFA3F17C34353C50B6E828E5AC73F561E854F357F7602A9F7CFE276C9D74C83EEC2C9F77C5B054742DD9B4469C4B
tools\git2-6777db8.pdb
 
tools\gitversion.exe
md5: 9AD864D79E1C682D75F41537768D971D | sha1: F96B7C31F1BB9022C07170E21EF2482C39E7FBD7 | sha256: 04EB0525BD6CCC6FB944238A30F40D7DEFEBF4F156D785D4244EF2A27D433CD1 | sha512: 7D38E7935754BA51948A376D361E172836F58689E8ECE8461E410208965FAC085A1D665FABF5DD3E319A0C7B7D59AB01FFBBB27953848141EE2B1028ABEF87BF
tools\GitVersion.xml
<?xml version="1.0"?>
<doc>
    <assembly>
        <name>gitversion</name>
    </assembly>
    <members>
    </members>
</doc>
tools\GitVersionCore.xml
<?xml version="1.0"?>
<doc>
    <assembly>
        <name>GitVersionCore</name>
    </assembly>
    <members>
        <member name="M:GitVersion.BuildAgents.Jenkins.ShouldCleanUpRemotes">
            <summary>
            When Jenkins uses pipeline-as-code, it creates two remotes: "origin" and "origin1".
            This should be cleaned up, so that normizaling the Git repo will not fail.
            </summary>
            <returns></returns>
        </member>
        <member name="M:GitVersion.Configuration.IBranchConfigurationCalculator.GetBranchConfiguration(LibGit2Sharp.Branch,LibGit2Sharp.Commit,GitVersion.Model.Configuration.Config,System.Collections.Generic.IList{LibGit2Sharp.Branch})">
            <summary>
            Gets the <see cref="T:GitVersion.Model.Configuration.BranchConfig"/> for the current commit.
            </summary>
        </member>
        <member name="M:GitVersion.Configuration.BranchConfigurationCalculator.GetBranchConfiguration(LibGit2Sharp.Branch,LibGit2Sharp.Commit,GitVersion.Model.Configuration.Config,System.Collections.Generic.IList{LibGit2Sharp.Branch})">
            <summary>
            Gets the <see cref="T:GitVersion.Model.Configuration.BranchConfig"/> for the current commit.
            </summary>
        </member>
        <member name="T:GitVersion.IGitRepositoryCommands">
            <summary>
            Mockable and testable interface wrapper for the <c>static</c>
            <see cref="T:LibGit2Sharp.Commands"/> <c>class</c>.
            </summary>
        </member>
        <member name="M:GitVersion.Common.IRepositoryMetadataProvider.FindMergeBase(LibGit2Sharp.Branch,LibGit2Sharp.Branch)">
            <summary>
            Find the merge base of the two branches, i.e. the best common ancestor of the two branches' tips.
            </summary>
        </member>
        <member name="M:GitVersion.Common.IRepositoryMetadataProvider.FindCommitBranchWasBranchedFrom(LibGit2Sharp.Branch,GitVersion.Model.Configuration.Config,LibGit2Sharp.Branch[])">
            <summary>
            Find the commit where the given branch was branched from another branch.
            If there are multiple such commits and branches, tries to guess based on commit histories.
            </summary>
        </member>
        <member name="M:GitVersion.GitPreparer.NormalizeGitDirectory(System.String,System.Boolean,System.String,System.Boolean)">
            <summary>
            Normalization of a git directory turns all remote branches into local branches, turns pull request refs into a real branch and a few other things. This is designed to be run *only on the build server* which checks out repositories in different ways.
            It is not recommended to run normalization against a local repository
            </summary>
        </member>
        <member name="T:GitVersion.GitRepositoryCommands">
            <summary>
            Default implementation of <see cref="T:GitVersion.IGitRepositoryCommands"/> using
            the <c>static</c> <see cref="T:LibGit2Sharp.Commands"/> <c>class</c>.
            </summary>
        </member>
        <member name="M:GitVersion.RepositoryMetadataProvider.FindMergeBase(LibGit2Sharp.Branch,LibGit2Sharp.Branch)">
            <summary>
            Find the merge base of the two branches, i.e. the best common ancestor of the two branches' tips.
            </summary>
        </member>
        <member name="M:GitVersion.RepositoryMetadataProvider.FindCommitBranchWasBranchedFrom(LibGit2Sharp.Branch,GitVersion.Model.Configuration.Config,LibGit2Sharp.Branch[])">
            <summary>
            Find the commit where the given branch was branched from another branch.
            If there are multiple such commits and branches, tries to guess based on commit histories.
            </summary>
        </member>
        <member name="M:GitVersion.Extensions.LibGitExtensions.IsSameBranch(LibGit2Sharp.Branch,LibGit2Sharp.Branch)">
            <summary>
            Checks if the two branch objects refer to the same branch (have the same friendly name).
            </summary>
        </member>
        <member name="M:GitVersion.Extensions.LibGitExtensions.ExcludingBranches(System.Collections.Generic.IEnumerable{GitVersion.BranchCommit},System.Collections.Generic.IEnumerable{LibGit2Sharp.Branch})">
            <summary>
            Exclude the given branches (by value equality according to friendly name).
            </summary>
        </member>
        <member name="M:GitVersion.Extensions.LibGitExtensions.ExcludingBranches(System.Collections.Generic.IEnumerable{LibGit2Sharp.Branch},System.Collections.Generic.IEnumerable{LibGit2Sharp.Branch})">
            <summary>
            Exclude the given branches (by value equality according to friendly name).
            </summary>
        </member>
        <member name="M:GitVersion.Extensions.ReadEmbeddedResourceExtensions.ReadAsStringFromEmbeddedResource``1(System.String)">
            <summary>
            
            </summary>
            <typeparam name="T"></typeparam>
            <param name="resourceName">Should include Namespace separated path to resource in assembly referenced by <typeparamref name="T"/></param>
            <returns></returns>
        </member>
        <member name="M:GitVersion.Helpers.EncodingHelper.DetectEncoding(System.String)">
            <summary>
            Detects the encoding of a file if and only if it includes a preamble .
            </summary>
            <param name="filename">The file name to check the encoding of.</param>
            <returns>The encoding of the file if it has a preamble otherwise null.</returns>
        </member>
        <member name="M:GitVersion.Helpers.EncodingHelper.DetectEncoding(System.Collections.Generic.IList{System.Byte})">
            <summary>
            Returns the first encoding where all the preamble bytes match exactly.
            </summary>
            <param name="bytes">The bytes to check for a matching preamble.</param>
            <returns>The encoding that has a matching preamble or null if one was not found.</returns>
        </member>
        <member name="M:GitVersion.Helpers.EncodingHelper.ScanEncodings">
            <summary>
            Returns an ordered list of encodings that have preambles ordered by the length of the
            preamble longest to shortest. This prevents a short preamble masking a longer one
            later in the list.
            </summary>
            <returns>An ordered list of encodings and corresponding preambles.</returns>
        </member>
        <member name="M:GitVersion.Helpers.EncodingHelper.PreambleMatches(System.Text.Encoding,System.Collections.Generic.IList{System.Byte})">
            <summary>
            Verifies that all bytes of an encoding's preamble are present at the beginning of some sample data.
            </summary>
            <param name="encoding">The encoding to check against.</param>
            <param name="data">The data to test.</param>
            <returns>A boolean indicating if a preamble match was found.</returns>
        </member>
        <member name="T:GitVersion.Helpers.ProcessHelper.NativeErrorCode">
            <summary>
            System error codes.
            See: https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382.aspx
            </summary>
        </member>
        <member name="M:GitVersion.Helpers.StringFormatWithExtension.FormatWith``1(System.String,``0,GitVersion.IEnvironment)">
            <summary>
            Formats the <paramref name="template"/>, replacing each expression wrapped in curly braces
            with the corresponding property from the <paramref name="source"/> or <paramref name="environment"/>.
            </summary>
            <param name="template" this="true">The source template, which may contain expressions to be replaced, e.g '{Foo.Bar.CurrencySymbol} foo {Foo.Bar.Price}'</param>
            <param name="source">The source object to apply to the <paramref name="template"/></param>
            <param name="environment"></param>
            <exception cref="T:System.ArgumentNullException">The <paramref name="template"/> is null.</exception>
            <exception cref="T:System.ArgumentException">An environment variable was null and no fallback was provided.</exception>
            <remarks>
            An expression containing "." is treated as a property or field access on the <paramref name="source"/>.
            An expression starting with "env:" is replaced with the value of the corresponding variable from the <paramref name="environment"/>.
            Each expression may specify a single hardcoded fallback value using the {Prop ?? "fallback"} syntax, which applies if the expression evaluates to null.
            </remarks>
            <example>
            // replace an expression with a property value
            "Hello {Name}".FormatWith(new { Name = "Fred" }, env);
            "Hello {Name ?? \"Fred\"}".FormatWith(new { Name = GetNameOrNull() }, env);
            // replace an expression with an environment variable
            "{env:BUILD_NUMBER}".FormatWith(new { }, env);
            "{env:BUILD_NUMBER ?? \"0\"}".FormatWith(new { }, env);
            </example>
        </member>
        <member name="T:GitVersion.BranchCommit">
            <summary>
            A commit, together with the branch to which the commit belongs.
            </summary>
        </member>
        <member name="M:GitVersion.Model.Configuration.BranchConfig.#ctor(GitVersion.Model.Configuration.BranchConfig)">
            <summary>
            Creates a clone of the given <paramref name="branchConfiguration"/>.
            </summary>
        </member>
        <member name="P:GitVersion.Model.Configuration.BranchConfig.Tag">
            <summary>
            Special value 'useBranchName' will extract the tag from the branch name
            </summary>
        </member>
        <member name="P:GitVersion.Model.Configuration.BranchConfig.Name">
            <summary>
            The name given to this configuration in the config file.
            </summary>
        </member>
        <member name="T:GitVersion.Model.Configuration.EffectiveConfiguration">
            <summary>
            Configuration can be applied to different things, effective configuration is the result after applying the appropriate configuration
            </summary>
        </member>
        <member name="P:GitVersion.Model.Configuration.EffectiveConfiguration.GitTagPrefix">
            <summary>
            Git tag prefix
            </summary>
        </member>
        <member name="P:GitVersion.Model.Configuration.EffectiveConfiguration.Tag">
            <summary>
            Tag to use when calculating SemVer
            </summary>
        </member>
        <member name="T:GitVersion.GitVersionContext">
            <summary>
            Contextual information about where GitVersion is being run
            </summary>
        </member>
        <member name="P:GitVersion.GitVersionContext.FullConfiguration">
            <summary>
            Contains the raw configuration, use Configuration for specific config based on the current GitVersion context.
            </summary>
        </member>
        <member name="M:GitVersion.VersionCalculation.IVersionStrategy.GetVersions">
            <summary>
            Calculates the <see cref="T:GitVersion.VersionCalculation.BaseVersionCalculators.BaseVersion" /> values.
            </summary>
            <returns>
            An <see cref="T:System.Collections.Generic.IEnumerable`1" /> of the base version values found by the strategy.
            </returns>
        </member>
        <member name="T:GitVersion.VersionCalculation.ConfigNextVersionVersionStrategy">
            <summary>
            Version is from NextVersion (the configuration value), unless the current commit is tagged.
            BaseVersionSource is null.
            Does not increment.
            </summary>
        </member>
        <member name="T:GitVersion.VersionCalculation.FallbackVersionStrategy">
            <summary>
            Version is 0.1.0.
            BaseVersionSource is the "root" commit reachable from the current commit.
            Does not increment.
            </summary>
        </member>
        <member name="T:GitVersion.VersionCalculation.MergeMessageVersionStrategy">
            <summary>
            Version is extracted from older commits's merge messages.
            BaseVersionSource is the commit where the message was found.
            Increments if PreventIncrementForMergedBranchVersion (from the branch config) is false.
            </summary>
        </member>
        <member name="T:GitVersion.VersionCalculation.TaggedCommitVersionStrategy">
            <summary>
            Version is extracted from all tags on the branch which are valid, and not newer than the current commit.
            BaseVersionSource is the tag's commit.
            Increments if the tag is not the current commit.
            </summary>
        </member>
        <member name="T:GitVersion.VersionCalculation.TrackReleaseBranchesVersionStrategy">
            <summary>
            Active only when the branch is marked as IsDevelop.
            Two different algorithms (results are merged):
            <para>
            Using <see cref="T:GitVersion.VersionCalculation.VersionInBranchNameVersionStrategy"/>:
            Version is that of any child branches marked with IsReleaseBranch (except if they have no commits of their own).
            BaseVersionSource is the commit where the child branch was created.
            Always increments.
            </para>
            <para>
            Using <see cref="T:GitVersion.VersionCalculation.TaggedCommitVersionStrategy"/>:
            Version is extracted from all tags on the <c>master</c> branch which are valid.
            BaseVersionSource is the tag's commit (same as base strategy).
            Increments if the tag is not the current commit (same as base strategy).
            </para>
            </summary>
        </member>
        <member name="T:GitVersion.VersionCalculation.VersionInBranchNameVersionStrategy">
            <summary>
            Version is extracted from the name of the branch.
            BaseVersionSource is the commit where the branch was branched from its parent.
            Does not increment.
            </summary>
        </member>
        <member name="M:GitVersion.VersionCalculation.MainlineVersionCalculator.GetEffectiveMainlineTip(System.Collections.Generic.IEnumerable{LibGit2Sharp.Commit},LibGit2Sharp.Commit,LibGit2Sharp.Commit)">
            <summary>
            Gets the commit on mainline at which <paramref name="mergeBase"/> was fully integrated.
            </summary>
            <param name="mainlineCommitLog">The collection of commits made directly to mainline, in reverse order.</param>
            <param name="mergeBase">The best possible merge base between <paramref name="mainlineTip"/> and the current commit.</param>
            <param name="mainlineTip">The tip of the mainline branch.</param>
            <returns>The commit on mainline at which <paramref name="mergeBase"/> was merged, if such a commit exists; otherwise, <paramref name="mainlineTip"/>.</returns>
            <remarks>
            This method gets the most recent commit on mainline that should be considered for versioning the current branch.
            </remarks>
        </member>
        <member name="M:GitVersion.VersionCalculation.MainlineVersionCalculator.FindMergeBaseBeforeForwardMerge(LibGit2Sharp.Commit,LibGit2Sharp.Branch,[email protected])">
            <summary>
            Gets the best possible merge base between the current commit and <paramref name="mainline"/> that is not the child of a forward merge.
            </summary>
            <param name="baseVersionSource">The commit that establishes the contextual base version.</param>
            <param name="mainline">The mainline branch.</param>
            <param name="mainlineTip">The commit on mainline at which the returned merge base was fully integrated.</param>
            <returns>The best possible merge base between the current commit and <paramref name="mainline"/> that is not the child of a forward merge.</returns>
        </member>
        <member name="F:GitVersion.IncrementStrategy.Inherit">
            <summary>
            Uses the <see cref="P:GitVersion.Model.Configuration.BranchConfig.Increment"/>, <see cref="P:GitVersion.Model.Configuration.BranchConfig.PreventIncrementOfMergedBranchVersion"/> and <see cref="P:GitVersion.Model.Configuration.BranchConfig.TracksReleaseBranches"/>
            of the "parent" branch (i.e. the branch where the current branch was branched from).
            </summary>
        </member>
        <member name="M:GitVersion.SemanticVersion.ToString(System.String,System.IFormatProvider)">
            <summary>
            <para>s - Default SemVer [1.2.3-beta.4+5]</para>
            <para>f - Full SemVer [1.2.3-beta.4+5]</para>
            <para>i - Informational SemVer [1.2.3-beta.4+5.Branch.master.BranchType.Master.Sha.000000]</para>
            <para>j - Just the SemVer part [1.2.3]</para>
            <para>t - SemVer with the tag [1.2.3-beta.4]</para>
            <para>l - Legacy SemVer tag for systems which do not support SemVer 2.0 properly [1.2.3-beta4]</para>
            <para>lp - Legacy SemVer tag for systems which do not support SemVer 2.0 properly (padded) [1.2.3-beta0004]</para>
            </summary>
        </member>
        <member name="M:GitVersion.SemanticVersionBuildMetaData.ToString(System.String,System.IFormatProvider)">
            <summary>
            <para>b - Formats just the build number</para>
            <para>s - Formats the build number and the Git Sha</para>
            <para>f - Formats the full build metadata</para>
            <para>p - Formats the padded build number. Can specify an integer for padding, default is 4. (i.e., p5)</para>
            </summary>
        </member>
        <member name="M:GitVersion.SemanticVersionPreReleaseTag.ToString(System.String,System.IFormatProvider)">
            <summary>
            Default formats:
            <para>t - SemVer 2.0 formatted tag [beta.1]</para>
            <para>l - Legacy SemVer tag with the tag number padded. [beta1]</para>
            <para>lp - Legacy SemVer tag with the tag number padded. [beta0001]. Can specify an integer to control padding (i.e., lp5)</para>
            </summary>
        </member>
    </members>
</doc>
tools\LICENSE.txt
The MIT License (MIT)

Copyright (c) 2013 NServiceBus Ltd

Permission is hereby granted, free of charge, to any person obtaining a copy of
this software and associated documentation files (the "Software"), to deal in
the Software without restriction, including without limitation the rights to
use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of
the Software, and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
tools\mscordaccore.dll
md5: BE504E246229F9D571332BA438334278 | sha1: 0EF2C97723946BCE230ADBFB394FDB509E37066A | sha256: E02E75F03A4B5447B0C9207FF06422576910C3A7A467160479F1CA997BAAECA7 | sha512: 70A24D8BC77DEF92F39D4F1F8C3124715D3A131FB84277E6AB935180F7A0F97729FBAD4A5D9E4A18D55EBAD4FACC75C03A34101D2125AC25AB0A2F582636031D
tools\VERIFICATION.txt
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the GitTools organization itself. The binaries are
identical to other package types published by the project, in particular
the GitVersion.Portable nuget package.

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.8 2617 Tuesday, April 6, 2021 Approved
GitVersion 5.6.7 607 Thursday, March 25, 2021 Approved
GitVersion 5.6.6 5565 Wednesday, February 10, 2021 Approved
GitVersion 5.6.5 592 Sunday, February 7, 2021 Approved
GitVersion 5.6.4 2599 Tuesday, January 19, 2021 Approved
GitVersion 5.6.3 1836 Friday, January 8, 2021 Approved
GitVersion 5.6.2 75 Friday, January 8, 2021 Approved
GitVersion 5.6.1 790 Sunday, January 3, 2021 Approved
GitVersion 5.6.0 1432 Saturday, December 19, 2020 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