macOS
Homebrewverified · 100%
brew install gitversionlocal Homebrew formula metadata
brew
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
Additional install commands
Windows
Chocolateyverified · 92%
choco install GitVersionChocolatey community package catalog · GitVersion · source: community.chocolatey.org
Scoopverified · 92%
scoop install main/gitversionScoop official bucket manifest trees · bucket/gitversion.json · source: api.github.com
Windows Package Managerverified · 92%
winget install --id GitTools.GitVersion -eWindows Package Manager source index · GitTools.GitVersion · source: cdn.winget.microsoft.com
overview
Package summary
Easy semantic versioning for projects using Git
Project links
Commands and aliases
- gitversion
history
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 posture
Risk level: green
narrow executable package without higher-risk signals.
Risk classifier
green risk · low confidence · appliance
Why
- narrow executable package without higher-risk signals
Signals
- metadata:no-higher-risk-signals
Install behavior
- No Homebrew post-install hook is recorded in formula metadata.
- Homebrew bottle metadata is available for 6 platform targets.
- Installs with 2 runtime dependencies.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
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
Config paths the tool may read or write during local use.
- Unix
GitVersion.ymlGitVersion.yaml.GitVersion.yml.GitVersion.yaml- Windows
GitVersion.ymlGitVersion.yaml.GitVersion.yml.GitVersion.yaml
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
gitversion | cli | global executable |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-07-08
manager version6.8.1
manager updated2026-07-03
local dataok
upstreamcurrent
latest detected6.8.1
https://github.com/GitTools/GitVersion
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:gitversion |
|---|---|
| Version | 6.8.1 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/gitversion |
| Homepage | https://gitversion.net/docs/ |
| Repository | https://github.com/GitTools/GitVersion |
| Upstream docs | https://gitversion.net/docs |
| License | MIT |
| Source archive | https://github.com/GitTools/GitVersion/archive/refs/tags/6.8.1.tar.gz |
| Last updated | 2026-07-03T15:04:39Z |
| Pulse | updated |
| Dependencies | dotnet, openssl@3 |
| Bottle | available (on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
registry facts
Source database details
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | gitversion |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Other package-manager records
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
Chocolatey95%
GitVersion
choco install GitVersion- normalized package name match
- Matched by: Gitversion
Scoop95%
main/gitversion
scoop install main/gitversion- normalized package name match
- Matched by: Gitversion
winget95%
GitTools.GitVersion
winget install --id GitTools.GitVersion -e- normalized package name match
- Matched by: Gitversion
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- Nucleus package database
- av.db category and tag curation
- cross-ecosystem install command graph
- curated configuration and credential file locations
- curated package history
- external package-manager database matches
- package relationship graph
- package version freshness
- package-page enrichment