# Installer gitversion avec Homebrew, chocolatey, scoop, winget
Consultez les chemins d'installation, exécutables, métadonnées et notes de sécurité de gitversion pour les workflows d'agents IA.
## installation
```sh
sudo av install brew:gitversion
```
Commandes d'installation supplémentaires:
### macOS
- Homebrew (100%):
```sh
brew install gitversion
```
Preuve: local Homebrew formula metadata
### Windows
- Chocolatey (92%):
```sh
choco install GitVersion
```
Preuve: Chocolatey community package catalog: GitVersion from http://community.chocolatey.org/api/v2/Packages?$filter=IsLatestVersion&$select=Id&$top=1000&$skiptoken='6.928','obs-virtualcam'
- Scoop (92%):
```sh
scoop install main/gitversion
```
Preuve: 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
```
Preuve: Windows Package Manager source index: GitTools.GitVersion from https://cdn.winget.microsoft.com/cache/source.msix
## Faits du paquet
- **Clé du paquet:** brew:gitversion
- **Gestionnaire de paquets:** Homebrew
- **Version:** 6.8.2
- **Résumé source:** Easy semantic versioning for projects using Git
- **Page d'accueil:**
- **Dépôt:**
- **Dernière mise à jour:** 2026-07-10T09:37:05Z
- **Généré:** 2026-08-03T19:37:03+00:00
## exécutables
- gitversion (alias)
## Comportement d'installation
- Bouteille: non disponible
## Version et fraîcheur
- page générée: 2026-08-03
- version du gestionnaire: 6.8.2
## Historique du projet et usages
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.
### Historique du projet
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.
### Historique d'adoption
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.
### Modes d'utilisation
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.
### Pourquoi les passionnés de paquets s'y intéressent
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.
### Chronologie
- 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
-
-
-
-
-
## Notes de sécurité
narrow executable package without higher-risk signals.
- **Risque Geiger:** vert / faible
- 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
## Autres enregistrements de gestionnaires de paquets
- 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.928','obs-virtualcam'
- 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
## Combined YAML source
View the package source record on GitHub. [combined/gitversion.yml](https://github.com/mxcl/pkgdb/blob/main/combined/gitversion.yml)
## Sources
- pkg.so package database
- Geiger risk classifier
- curated configuration and credential file locations
- curated package history
- pkgdb category and tag curation
- external package-manager database matches
- cross-ecosystem install command graph