# Install gitversion with Homebrew, chocolatey, scoop, winget Easy semantic versioning for projects using Git. Version 6.8.1 via Homebrew; verified 2026-07-03. ## Install ```sh sudo av install brew:gitversion ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install gitversion ``` Evidence: local Homebrew formula metadata ### Windows - Chocolatey (92%): ```sh choco install GitVersion ``` Evidence: Chocolatey community package catalog: GitVersion from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.5836','capture' - Scoop (92%): ```sh scoop install main/gitversion ``` Evidence: Scoop official bucket manifest trees: bucket/gitversion.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget (92%): ```sh winget install --id GitTools.GitVersion -e ``` Evidence: Windows Package Manager source index: GitTools.GitVersion from https://cdn.winget.microsoft.com/cache/source.msix ## Package facts - **Package key:** brew:gitversion - **Package manager:** Homebrew - **Package manager page:** - **Version:** 6.8.1 - **Source summary:** Easy semantic versioning for projects using Git - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** MIT - **Source archive:** - **Last updated:** 2026-07-03T15:04:39Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - gitversion (cli) - gitversion (alias) ## Dependencies - dotnet - openssl@3 ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 6.8.1 - Package-manager updated: 2026-07-03 - Local data: ok - Upstream repository: https://github.com/GitTools/GitVersion - Upstream latest detected: 6.8.1 (current) ## Project history and usage GitVersion is a release-management utility that derives Semantic Versioning values from a Git repository. It turns branch names, tags, merge history, and configuration into version variables that can be consumed by command-line builds, MSBuild, CI tasks, Docker workflows, and libraries. ### Project history The GitTools/GitVersion repository dates to 2013 and grew around a narrow problem in Git-based release automation: projects wanted SemVer numbers without hand-editing version files on every build. Its official README describes the core idea as looking at Git history and working out the Semantic Version of the commit being built. The project evolved from a .NET-oriented CLI into a family of build integrations. The official README lists GitHub releases, Chocolatey, NuGet packages for the .NET tool and MSBuild task, Homebrew, Winget, Azure Pipelines, GitHub Actions, and Docker artifacts, reflecting a tool meant to sit inside many build systems rather than one local shell. ### Adoption history GitVersion became significant in the .NET and CI ecosystem because it encoded common GitFlow and trunk-style versioning rules into a repeatable build step. Its documentation emphasizes use in command-line and continuous-integration contexts, where build servers need the same version calculation as developer machines. Package-manager metadata in this batch shows GitVersion distributed through Homebrew, Chocolatey, Scoop, and Winget. Combined with the official NuGet, Azure Pipelines, GitHub Actions, and Docker artifacts, that spread shows adoption across local developer tooling and hosted build infrastructure. ### How it is used Practitioners use GitVersion to generate version variables during builds, then feed those values into package metadata, assembly attributes, container tags, release names, or CI outputs. The common workflow is to run the CLI or an integration from a checked-out Git repository and let GitVersion infer the SemVer value from repository state. Teams also add GitVersion.yml or GitVersion.yaml files when the default branching and incrementing rules need to match their release process. That configuration keeps version policy near source code while avoiding custom scripts for every pipeline. ### Why package nerds care GitVersion matters to package maintainers because it makes version numbers reproducible from source history. That is attractive for automated package builds, where the package version should be explainable from tags and commits rather than a mutable build-server counter. It is also a good example of a CLI that became a packaging surface in its own right: the same versioning engine is exposed as a standalone executable, a .NET tool, an MSBuild task, CI marketplace integrations, and container images. ### Timeline - 2013: The GitTools/GitVersion repository is created on GitHub. - 2015: GitVersion 3.3.0 appears in the GitHub releases feed. - 2020: GitVersion 5.x tags show the tool's continued shift toward broad build-system integration. - 2026: Repository activity and packaged artifacts show ongoing maintenance. ### Related projects - Semantic Versioning supplies the version-numbering convention GitVersion calculates. - GitFlow-style branch models influenced many of GitVersion's documented branch and incrementing rules. - GitHub Actions, Azure Pipelines, MSBuild, NuGet, Docker, Homebrew, Chocolatey, Scoop, and Winget are distribution or integration surfaces named by the project and package metadata. ### Sources - - - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Configuration and credential file locations These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval. ## Configuration files - Unix: GitVersion.yml, GitVersion.yaml, .GitVersion.yml, .GitVersion.yaml - Windows: GitVersion.yml, GitVersion.yaml, .GitVersion.yml, .GitVersion.yaml ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** gitversion - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Chocolatey - GitVersion: normalized package name match | Chocolatey community package catalog: GitVersion from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.5836','capture' - Scoop - main/gitversion: normalized package name match | Scoop official bucket manifest trees: bucket/gitversion.json from https://api.github.com/repos/ScoopInstaller/Main/git/trees/master?recursive=1 - winget - GitTools.GitVersion: normalized package name match | Windows Package Manager source index: GitTools.GitVersion from https://cdn.winget.microsoft.com/cache/source.msix ## Related links - [Source-control packages](https://www.automicvault.com/pkg/source-control-tools/) - Belongs to a source-control command family. - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [dotnet](https://www.automicvault.com/pkg/brew/dotnet/) - Runtime dependency declared by Homebrew. - [openssl@3](https://www.automicvault.com/pkg/brew/openssl-3/) - Runtime dependency declared by Homebrew. - [commitizen](https://www.automicvault.com/pkg/brew/commitizen/) - Shares av.db curated category or tags: cli, developer-tools, git, release-management, semantic-versioning. - [aicommit](https://www.automicvault.com/pkg/brew/aicommit/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. - [aicommit2](https://www.automicvault.com/pkg/brew/aicommit2/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. - [aicommits](https://www.automicvault.com/pkg/brew/aicommits/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. - [braid](https://www.automicvault.com/pkg/brew/braid/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. - [changelogen](https://www.automicvault.com/pkg/brew/changelogen/) - Shares av.db curated category or tags: cli, developer-tools, release-management, versioning. - [changie](https://www.automicvault.com/pkg/brew/changie/) - Shares av.db curated category or tags: cli, developer-tools, release-management, versioning. - [cig](https://www.automicvault.com/pkg/brew/cig/) - Shares av.db curated category or tags: cli, developer-tools, git, version-control. - [weave](https://www.automicvault.com/pkg/brew/weave/) - Local package facts share a topical domain. Shared terms: cli, control, developer, developer-tools, git. - [git-series](https://www.automicvault.com/pkg/brew/git-series/) - Local package facts share a topical domain. Shared terms: cli, control, developer, developer-tools, git. ## Combined YAML source View the package source record on GitHub. [combined/gitversion.yml](https://github.com/automic-vault/db/blob/main/combined/gitversion.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated configuration and credential file locations - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph