Git Credential Manager (User): all versions and old releases

Git Credential Manager 3.0 brings native ahead-of-time compilation, Microsoft authentication broker support across Windows, macOS, and Linux, and a refreshed terminal experience.
Changes since 3.0.0
- (Bug fix) Prompt for default OS account on Microsoft DevBox (#2459)
- (Bug fix) Restore Entra broker parent window handling (#2464)
- (Feature) Support authtype Git capability (#2457)
- (Feature) Add console parent window parenting for non-Entra UI (#2465)
- Drop Windows x86 release binaries (#2456)

Changes since 2.9.1
Important
This release changes supported operating systems and the default Azure Repos authentication experience. Review the breaking changes before upgrading.

Breaking changes and upgrade notes

Updated platform and .NET requirements
GCM now targets .NET 10 on all platforms. Windows builds no longer use .NET Framework.
───────────────────────────────┬─────────────────────────────────────────────────────────
Platform or installation method│Requirement
───────────────────────────────┼─────────────────────────────────────────────────────────
Windows │Windows 10 or later; Windows Server 2016 or later
───────────────────────────────┼─────────────────────────────────────────────────────────
macOS │macOS 14 or later
───────────────────────────────┼─────────────────────────────────────────────────────────
Linux │A distribution supported by .NET 10
───────────────────────────────┼─────────────────────────────────────────────────────────
.NET tool │Install the .NET 10 SDK before installing or updating GCM
───────────────────────────────┴─────────────────────────────────────────────────────────
See the supported environments and .NET 10 support matrix for details. Standalone platform packages do not require a separate .NET installation.
Windows 7 and Windows 8.x are no longer supported by GCM 3.x. GCM 2.9.x will receive minimal, security-only maintenance for those systems, but no new features. Upgrading Windows is recommended. (git-ecosystem/git-credential-manager#2365, git-ecosystem/git-credential-manager#2367)

Azure Repos uses OAuth tokens by default
GCM now returns Microsoft identity OAuth tokens, rather than creating personal access tokens (PATs), by default for Azure Repos. OAuth tokens are automatically refreshed as needed.
Explicit credential-type settings are still respected. If you need the previous PAT behavior, set:
git config --global credential.azreposCredentialType pat
The equivalent environment variable is GCM_AZREPOS_CREDENTIALTYPE=pat. See Azure Repos users and tokens. (git-ecosystem/git-credential-manager#2449)

Microsoft authentication uses the OS broker by default
Broker integration is now enabled by default wherever supported, rather than requiring an opt-in. This applies to Microsoft authentication, such as Azure Repos; it does not change authentication for GitHub, Bitbucket, or GitLab.
On macOS, broker authentication requires Company Portal and device enrollment. On Linux, it requires the supported Intune setup, a GNOME desktop, and Microsoft Edge; headless and WSL environments do not support the Linux broker.
Warning
Depending on your organization's policies, broker sign-in can prompt you to join or enroll your device. On Windows, signing in with a personal Microsoft account can also affect the account linked to your local Windows user. Review the broker documentation before proceeding, especially on personal devices.
To opt out:
git config --global credential.msauthUseBroker false
The equivalent environment variable is GCM_MSAUTH_USEBROKER=false. When the broker is in use, it takes precedence over credential.msauthFlow. (git-ecosystem/git-credential-manager#2449)

Azure Repos uses a dedicated GCM Entra application
GCM now signs in using its own first-party Microsoft Entra application instead of the Visual Studio application. This enables broker support on macOS and Linux, in addition to Windows.
If you encounter a client-application configuration error, GCM provides guidance for retrying with the 

Announcements:
Note
This is planned to be the last release major release (2.x) that supports Windows 7 and 8.x. We will be moving off of .NET Framework to .NET (Core) on Windows this year with version 3.0.
Changes:
- Use AbsoluteUri to open URIs in the system browser to avoid double encoded URLs on macOS (90884de)

Announcements:
Note
This is planned to be the last release major release that supports Windows 7 and 8.x. We will be moving off of .NET Framework to .NET (Core) on Windows this year.
Changes:
- Workload Identity Federation for Azure Repos (#2297)
- Git config caching to reduce git process calls
- #2268
- #2296
- #2298
- Dark theme support for OAuth authentication response pages (#2325)
- Allow installing on Azure Linux (#2269)
- Fix GPG ID lookup for .gpg-id in subdirectories (#2274)
- Fix CS0121 string.Split call ambiguity with .NET 8.0 (#2287)
- Fix SYSLIB0057 warning for X509Certificate2Collection.Import (#2326)
- Fix several small bugs (#2303)
- Migrate to .NET 10 (Mac/Linux) and adopt Central Package Management (#2313)
- Bump Tmds.DBus.Protocol from 0.16.0 to 0.21.3 (#2316)
- Azure Pipelines: specify pool.hostArchitecture correctly (#2323)
- Documentation updates
- #2283
- #2299
- Actions dependency updates
- #2242
- #2271
- #2272
- #2282
- #2301
- #2315

Announcements:
Note
This is planned to be the last release major release that supports Windows 7 and 8.x. We will be moving off of .NET Framework to .NET (Core) on Windows this year.
Changes:
- Emit new warning when Git has built-in NTLM support disabled.
As part of the fix for CVE-2025-66413, Git for Windows now disables built-in NTLM support by default.
Only if http.allowNTLMAuth is explicitly enabled will Git use NTLM authentication.
GCM will now display a warning message when it detects this scenario and presents options for re-enabling NTLM.

Announcements:
Note
Thanks to all our contributors who've been waiting for this release. It's been a year since the last release, which as many will note is highly unusual. Ownership issues of the project have meant that there was a freeze on releases and maintenance. This has now been resolved and we expect regular releases (approximately every 12 weeks; aligned with Git's release schedule), and engagement on our part with the community. Thank you for your patience.
Note
The code ownership/responsibility model of the Git Credential Manager project has changed. Microsoft will now maintain the core GCM platform (responsible for releases, and major architectural changes). The major Git host providers will be responsible for their plugins (e.g., GitHub for GitHub functionality, Azure DevOps for Azure Repos etc).
Note
This is planned to be the last release major release that supports Windows 7 and 8.x. We will be moving off of .NET Framework to .NET (Core) on Windows this year.
Changes:
- Fix Generic provider refresh token refresh logic (#1838)
- Allow unsafe remotes via config (#1721)
- Drop no longer needed GitLab OAuth params (#1538)
- No-op credential storage option (#1740)
- Fix TRACE2 logging (#1909)
- Linux ARM and ARM64 support
- #1633
- #2232
- Windows ARM64 and x64 support (#2230)
- Support Oracle Linux vis install-from-source (#2212)
- Linux install-from-source bug fixes
- #1757
- #2049
- #2052
- macOS enterprise defaults (#1811)
- Documentation updates & fixes
- #1713
- #1722
- #1884
- #2123
- #2154
- Fixes to CI & build
- #1746
- #1747
- #1752
- #2104
- #2217
- Use Azure Pipelines for official builds
- #2054
- #2176
- Actions dependency updates
- #1725
- #1751
- #1750
- #1760
- #1799
- #2022
- #2048
- #1989
- #2011
- #2029
- #2051
- #2050
- #2070
- #2080
- #2089
- #2088
- #2092
- #2189
- #2193