Git: baixar versões antigas

Changes since Git for Windows v2.56.0(2) (October 5th 2026)
This is a security fix release, addressing the eMudhra Intermediate CA Compromise. It also addresses Git LFS' CVE-2026-105803 by upgrading to v3.8.1.
New Features
- Comes with OpenSSH v10.6.P1.
- Comes with cURL v8.23.0.
- Comes with Git LFS v3.8.1.

Changes since Git for Windows v2.56.0 (September 28th 2026)
New Features
- Comes with OpenSSL v3.5.9.
- To help with fixing stale references to the Git Credential Manager after Git for Windows v2.56.0's MINGW64 → UCRT64 migration, a compatibility shim is now installed.
Bug Fixes
- Suppressing the user-wide Git config via GIT_CONFIG_GLOBAL=NUL was broken in v2.56.0 (surprisingly, as a consequence of the MINGW64 → UCRT64 migration), which was fixed.
- Fixed a bug in Git for Windows, v2.56.0, where the x64 Git executables lost their Authenticode signatures by mistake.
- An assertion was fixed that caused pushes to fail when the server requires a client certificate.

Changes since Git for Windows v2.55.0(5) (August 20th 2026)
Following the MSYS2 project, on which Git for Windows is based, Windows 8.1 support was dropped; In doing so, internal paths changed (/mingw64/bin/git.exe does not exist anymore, /ucrt64/bin/git.exe takes its role; if this breaks your setups, consider switching to /cmd/git.exe instead, which is guaranteed to stay stable).
An issue with the installer for the previous version (v2.55.0.windows.5) caused the "Use external OpenSSH" option to be disabled for some users. This caused the bundled version of OpenSSH to be installed and overwrote any previously-saved choice of external OpenSSH. If you rely on an external OpenSSH installation, and you updated to v2.55.0(5), you should consider re-running the latest installer with "Only show new options" unchecked so that you can re-enable the external OpenSSH option. The bundled version of OpenSSH will be uninstalled automatically. If you do not rely on an external OpenSSH installation, or you did not install v2.55.0(5) specifically, you can safely ignore this notice.
New Features
- Comes with Git v2.56.0.
- Comes with Git LFS v3.8.0.
- Comes with cURL v8.22.0.
- Comes with OpenSSL v3.5.8.
Bug Fixes
- The installer is now actually a 64-bit one, which fixes the problem that the external OpenSSH option was broken in Git for Windows v2.55.0(5) (see notice above).
- It is now finally possible to commit 4GB objects or larger in Git for Windows.
- Fixes a bug where parallel checkouts could abort with "*** stack smashing detected ***: terminated".
- A bug introduced in Git for Windows v2.55.0(5), which caused vim to often open existing files with the first line missing, was fixed.
- git difftool will no longer crash upon encountering filenames that are illegal on Windows.

Changes since Git for Windows v2.55.0(4) (August 11th 2026)
Following the MSYS2 project, on which Git for Windows is based, Windows 8.1 support will be dropped after Git for Windows v2.55.
New Features
- The experimental git survey command (which was never upstreamed to the core Git project) was deprecated and converted into a small shim on top of git repo structure. In the future, git repo structure should be used instead, as the git survey command will be retired eventually.
- Git for Windows' installer is now a 64-bit executable (x64 instead of 86).
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.10.
- Comes with OpenSSH v10.5.P1.
Bug Fixes
- The long-standing bug where Git Bash's screen was cleared after git.exe called vim (e.g. to edit a commit message) was fixed.
- The Bash executables in the 64-bit and ARM64 distributions no longer carry an invalid Authenticode signature.

Changes since Git for Windows v2.55.0(3) (July 14th 2026)
Following the MSYS2 project, on which Git for Windows is based, Windows 8.1 support will be dropped after Git for Windows v2.55.
This is a security fix release, addressing CVE-2026-62960.
- CVE-2026-62960, Git for Windows: Attacker-controlled servers may advertise bundle URIs that point to network shares, causing Windows to transparently perform NTLM authentication and disclose the user's NTLMv2 hash. Since NTLM hashing is weak, the captured hash can potentially be brute-forced to recover the user's credentials. This is addressed by limiting the bundle URIs that git clone respects by the same protocol.<name>.allow rules as usual, which excludes file:// URIs by default.

Changes since Git for Windows v2.55.0(2) (July 2nd 2026)
New Features
- Comes with Git Credential Manager v2.9.0.
Bug Fixes
- Fixes heap overflows in the credential helper wincred, see GHSA-rxqw-wxqg-g7hw for full details.

Changes since Git for Windows v2.55.0 (June 29th 2026)
Following the MSYS2 project, on which Git for Windows is based, Windows 8.1 support will be dropped after Git for Windows v2.55.
Bug Fixes
- NTLM opt-in support, which had been prematurely disabled altogether (a glimpse into this fall when NTLM will be disabled, no opt-in possible) was fixed by temporarily enabling optional NTLM support again.

Changes since Git for Windows v2.54.0 (April 20th 2026)
Following the MSYS2 project, on which Git for Windows is based, Windows 8.1 support will be dropped after Git for Windows v2.55.
New Features
- Comes with Git v2.55.0.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.9.
- Comes with Git Credential Manager v2.8.0.
- Comes with less 702.
- The FSCache now accelerates more git add scenarios.
- Comes with OpenSSL v3.5.7.
- The diff helper handling Word documents was ported from Perl to Rust.
- Comes with Bash v5.3.15.
- Comes with cURL v8.21.0.
Bug Fixes
- A regression in v2.54.0 that could cause endless "Unlink of file '.git/objects/pack/pack-.idx' failed. Should I try again?" loops on older Windows 10 versions during git fetch operations was fixed.
- A bug that prevented proper shutdown of processes launched via Git Bash under certain circumstances was fixed.
- A bug was fixed which could cause parallel checkouts to fail under certain circumstances when the FSCache is enabled.
- Git Bash (MinTTY) now respects screen scaling settings under more circumstances.
- A couple of bugs revolving around very large clones/packfiles/objects were fixed.
- Following TortoiseGit v2.19, .git file validations have been tightened. As a consequence, access to remote repositories via UNC file paths needs to be allowed explicitly via the safe.directory configuration.

Changes since Git for Windows v2.53.0(3) (April 14th 2026)
Due to persistent maintenance challenges, git svn is no longer included in Git for Windows. Users who still need this command are highly encouraged to use a Linux version of git svn via the Windows Subsystem for Linux instead, or switch to a regular MSYS2 setup: install MSYS2, then run the following command in the MSYS2 UCRT64 Bash: pacman -Sy mingw-w64-ucrt-x86_64-git-svn. After that, the git svn command will be available in that Bash. On Windows/ARM64, you will want to use the CLANGARM64 variant instead (and install mingw-w64-clang-aarch64-git-svn).
New Features
- Comes with Git v2.54.0.
- Comes with Bash v5.3.9.
- Comes with Git Credential Manager v2.7.3.
- Comes with MinTTY v3.8.2.
- The shell aliases in Git Bash that ensured that interpreters such as Python and Node.JS are executed via winpty are no longer necessary, and have therefore been dropped.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.7.
- Comes with cURL v8.19.0.
- Comes with OpenSSH v10.3.P1.
- Comes with OpenSSL v3.5.6.
Bug Fixes
- The iconv executable, which was inadvertently dropped from Git for Windows v2.53.0's installer, is now included again.
- In some circumstances, when typing while a still-running program is about to terminate, the typed characters could arrive out of order in Git Bash. This bug was fixed.
- Similar to how git clean already avoids traversing NTFS junctions, git worktree remove now does the same.
- The number of CPU cores is now detected correctly on multi-socket systems.
- When fetching/pushing via Secure Channel (the default TLS/SSL method), the timeout to renegotiate (e.g. using client certificates) was recently reduced to 7 seconds, which was too short. It has been extended to 60 seconds.
- The recent security bug fix that disables NTLM by default missed the NTLM fallback in the Kerberos protocol. This fallback is now disabled, following the cURL project's guidance.
- A really old bug which prevented Kerberos authentication from working with the default http.emptyAuth ("auto"), was fixed.
- The git instaweb command is no longer distributed with Git for Windows because it would require GitWeb (which has not been distributed with Git for Windows for quite a few years).

Changes since Git for Windows v2.53.0(2) (March 10th 2026)
This is a security fix release, addressing CVE-2026-32631.
- CVE-2026-32631, Git for Windows: When a user clones a repository containing symbolic links pointing to network drives, Git follows those symlinks during checkout, causing Windows to transparently perform NTLM authentication and disclose the user's NTLMv2 hash to an attacker-controlled server. Since NTLM hashing is weak, the captured hash can potentially be brute-forced to recover the user's credentials. This is addressed by preventing git clone from following symbolic links that point to network drives during checkout.

Changes since Git for Windows v2.53.0 (February 2nd 2026)
This is a security fix release, addressing CVE-2025-66413.
- CVE-2025-66413, Git for Windows: When a user clones a repository from an attacker-controlled server, Git may attempt NTLM authentication and disclose the user's NTLMv2 hash to the remote server. Since NTLM hashing is weak, the captured hash can potentially be brute-forced to recover the user's credentials. This is addressed by disabling NTLM authentication by default.

Changes since Git for Windows v2.52.0 (November 17th 2025)
New Features
- Comes with Git v2.53.0.
- Pressing the Tab key in an empty line in Git Bash no longer causes the session to "freeze".
- Git for Windows' installer is now built by InnoSetup v6.6.1.
- Comes with cURL v8.18.0.
- Microsoft Edit can now be specified as Git editor.
- Comes with Git Credential Manager v2.7.0, the "anniversary release" after one release-less year, which brings native x64 and ARM64 binaries for the respective flavors of Git for Windows.
- Upgrades the memory allocator mimalloc that is used by Git for Windows to v2.2.7.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.6.
- Comes with OpenSSL v3.5.5.
Bug Fixes
- The installer of Git for Windows v2.52 showed clipped text in some setups, which was fixed.
- When calling Microsoft Store apps, their standard I/O is now set up correctly (meaning: You can call an interactive Python interpreter without the winpty hack mentioned in the release notes' Known Issues).
- The astextplain tool (which is used by Git for Windows to generate diffs of .pdf and .doc files) used to handle empty files gracefully. This behavior is now reinstated.

Changes since Git for Windows v2.51.2 (October 28th 2025)
As announced in several recent release notes, git svn is no longer supported by the Git for Windows project.
New Features
- Comes with Git v2.52.0.
- Comes with PCRE2 v10.47.
- Comes with cURL v8.17.0.
- The Git for Windows installer is now built with version 6.6.0 of InnoSetup, giving it a more modern look.
Bug Fixes
- The command git help git-bash was broken by a change in upstream Git v2.49.0, which has been fixed.

Changes since Git for Windows v2.51.1 (October 17th 2025)
New Features
- Comes with Git v2.51.2.
Bug Fixes
- The default credential helper in the portable variant of Git for Windows (credential-helper-selector) is now high DPI aware.

Changes since Git for Windows v2.51.0(2) (September 29th 2025)
This is a security release! Git LFS (which is enabled by default in Git for Windows) fixes CVE-2025-26625 (Severity rated High, 8.6 / 10) in v3.7.1. Please only clone or pull from repositories you trust until you upgraded.
Due to persistent maintenance challenges and the community's limited engagement and usage, git svn support in Git for Windows will be dropped from the next major Git for Windows release.
Note that git flow is no longer shipped with Git for Windows, after a version had been distributed that had been languishing for years. Even the original, years-stale Git Flow project has been archived.
New Features
- Comes with Git v2.51.1.
- Comes with Git LFS v3.7.1, addressing CVE-2025-26625.
- Comes with OpenSSL v3.5.4.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.5.
- Comes with OpenSSH v10.2.P1.
- Drops git flow.
Bug Fixes
- A potential memory corruption in the optional wincred credential helper was fixed.

Changes since Git for Windows v2.51.0 (August 19th 2025)
New Features
- Comes with PCRE2 v10.46.
- Comes with cURL v8.16.0. This addresses a bug where fetches/pushes could fail with failed to read data from server: SEC_E_CONTEXT_EXPIRED (0x80090317) under certain circumstances. Also included: a back-port of a fix for a bug where connection failures were mistakenly reported as time-outs.
- Comes with Tig v2.6.0.
- Comes with MinTTY v3.8.1.
- Comes with OpenSSL v3.5.3.
Bug Fixes
- The auto-updater now shows Git for Windows icon in the notification also on Windows/ARM64.
- git clone/git fetch now deals more gracefully with directory / file conflicts when the files backend is used for ref storage, by failing only the ones that are involved in the conflict while allowing others. This is a regression in Git v2.51.0 that was reported in Git for Windows and independently also to the Git mailing list. This was fixed by merging Git's topic branch kn/refs-files-case-insensitive.
- Support for pathspecs in diff --no-index was somewhat buggy, which has been fixed.
- git sparse-checkout subcommand learned a new clean action to prune otherwise unused working-tree files that are outside the areas of interest. An earlier version of this had been integrated into Microsoft Git already. This was fixed by merging Git's topic branch ds/sparse-checkout-clean.
- git rebase -i failed to clean-up the commit log message when the command commits the final one in a chain of "fixup" commands, which has been corrected. Backported from Git's topic branch pw/rebase-i-cleanup-fix.
- git subtree did not work correctly when splitting squashed subtrees, which has been improved. Backported from Git's topic branch cs/subtree-squash-split-fix.
- Some among git add -p and friends ignored color.diff and/or color.ui configuration variables, which is an old regression, which has been corrected. This was fixed by merging Git's topic branch jk/add-i-color.
- A corner-case bug in git log -L... has been corrected. This was fixed by merging Git's topic branch sg/line-log-boundary-fixes.
- A broken or malicious git fetch can say that it has the same object for many many times, and the upload-pack serving it can exhaust memory storing them redundantly, which has been corrected. This was fixed by merging Git's topic branch ps/upload-pack-oom-protection.
- Fixes multiple crashes around midx write-out codepaths. This was fixed by merging Git's topic branch ds/midx-write-fixes.
- git repack --path-walk lost objects in some corner cases, which has been corrected. This was fixed by merging Git's topic branch ds/path-walk-repack-fix.
- Under a race against another process that is repacking the repository, especially a partially cloned one, git fetch may mistakenly think some objects we do have are missing, which has been corrected. This was fixed by merging Git's topic branch jk/fetch-check-graph-objects-fix.
- Various options to git diff that makes comparison ignore certain aspects of the differences (like "space changes are ignored", "differences in lines that match these regular expressions are ignored") did not work well with --name-only and friends. This was fixed by merging Git's topic branch ly/diff-name-only-with-diff-from-content.
- git diff --no-index run inside a subdirectory under control of a Git repository operated at the top of the working tree and stripped the prefix from the output, and oddballs like "-" (stdin) did not work correctly because of it. Correct the set-up by undoing what the set-up sequence did to the current working directory and prefix. This was fixed by merging Git's topic branch jc/diff-no-index-in-subdir.
- Various bugs about rename handling in "ort" merge strategy have been fixed. This was fixed by merging Git's topic branch en/ort-rename-fixes.
- git push had a code path that led to BUG() but it should have reported a regular failure, as it is a response to a usual but invalid end-user action to attempt pushing an object that does not exist. This 

Changes since Git for Windows v2.50.1 (July 8th 2025)
New Features
- Comes with Git v2.51.0.
- The Portable Git installers (which are self-extracting 7-Zip archives) are now based off of 7-Zip 25.01
- Comes with cURL v8.15.0.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.4.
- Comes with MinTTY v3.7.9.

Changes since Git for Windows v2.50.0(2) (July 1st 2025)
This is a security fix release, addressing CVE-2024-50349, CVE-2024-52006, CVE-2025-27613, CVE-2025-27614, CVE-2025-46334, CVE-2025-46835, CVE-2025-48384, CVE-2025-48385, and CVE-2025-48386.
New Features
- Comes with Git v2.50.1.
Bug Fixes
- CVE-2025-27613, Gitk: When a user clones an untrusted repository and runs Gitk without additional command arguments, any writable file can be created and truncated. The option "Support per-file encoding" must have been enabled. The operation "Show origin of this line" is affected as well, regardless of the option being enabled or not.
- CVE-2025-27614, Gitk: A Git repository can be crafted in such a way that a user who has cloned the repository can be tricked into running any script supplied by the attacker by invoking gitk filename, where filename has a particular structure.
- CVE-2025-46334, Git GUI (Windows only): A malicious repository can ship versions of sh.exe or typical textconv filter programs such as astextplain. On Windows, path lookup can find such executables in the worktree. These programs are invoked when the user selects "Git Bash" or "Browse Files" from the menu.
- CVE-2025-46835, Git GUI: When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite any writable file.
- CVE-2025-48384, Git: When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout.
- CVE-2025-48385, Git: When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution.
- CVE-2025-48386, Git: The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows.
Note: As a courtesy, this release includes a last, unplanned, "after warranty" 32-bit installer.

Changes since Git for Windows v2.50.0 (June 16th 2025)
New Features
- Comes with Git LFS v3.7.0.
Bug Fixes
- Cloning large repositories via SSH frequently hung with Git for Windows v2.50.0, which was fixed.
- In Git for Windows v2.50.0, operations using the POSIX emulation layer (cloning via SSH, generating the Bash prompt) cannot be interrupted by Ctrl+C, which has been fixed.
- Git for Windows v2.50.0 is unable to initialize Git repositories on Windows Server 2016, which has been fixed.

Changes since Git for Windows v2.49.0 (March 17th 2025)
New Features
- Comes with Git v2.50.0.
- Comes with MinTTY v3.7.8.
- Comes with OpenSSH v10.0.P1.
- Comes with cURL v8.14.1.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.6.3.
Bug Fixes
- On Windows Server 2022, Git v2.48.1 introduced a regression where it failed to write files on ReFS drives, which was fixed.
- Git for Windows 2.48.1 introduced a regression when fetching long branches under core.longPaths = true, which was fixed.
- Git for Windows' installer used a non-writable file for testing custom editors, which was fixed.

Changes since Git for Windows v2.48.1 (February 13th 2025)
Due to persistent maintenance challenges and the community's limited engagement and usage, git svn support in Git for Windows will be phased out over the next few months.
Git for Windows v2.48.1 was the last version to ship with the i686 ("32-bit") variant of the installer, portable Git and archive. Only 32-bit MinGit will be built for future versions, until April 2029.
New Features
- Comes with Git v2.49.0.
- Comes with OpenSSH v9.9.P2.
- Comes with PCRE2 v10.45.
- The previously-experimental --full-name-hash option has been accepted into upstream Git as --name-hash-version=2 and is no longer experimental.
- The git backfill command has been accepted into upstream Git; Its --batch-size=<n> option has been renamed to --min-batch-size=<n>, though.
Bug Fixes
- A change in upstream Git v2.48.0 broke renaming symlinks, which was fixed.
- On a recent Insider Windows version, users experienced the message: "Cygwin WARNING: Couldn't compute FAST_CWD pointer", which has been fixed.
- A bug has been fixed that, when calling git add -p from VS Code's internal terminal, after using the edit command, caused the internal terminal got stuck and no further command was accepted.
- The syntax highlighting of the nano editor was recently disabled in Git for Windows by mistake, which was fixed.

Changes since Git for Windows v2.47.1(2) (January 14th 2025)
Git for Windows v2.48.1 is the last version to ship with the i686 ("32-bit") variant of the installer, portable Git and archive. Only 32-bit MinGit will be built for future versions, until April 2029.
Due to persistent maintenance challenges and the community's limited engagement and usage, git svn support in Git for Windows will be phased out over the next few months.
New Features
- Comes with Git v2.48.1.
- Comes with MinTTY v3.7.7.
- New Git for Windows installation now default to the Windows-native HTTPS transport backend.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.5.7 (Git for Windows skipped v3.5.5 because it failed to pass Git's test suite, and Cygwin v3.5.6 was superseded too quickly).
- Comes with Tig v2.5.12.
- Comes with cURL v8.12.1.
- Comes with OpenSSL v3.2.4.
Bug Fixes
- The installer now correctly blocks the installation on Windows 7 and Windows 8 as these versions of Windows are no longer supported since Git for Windows v2.47.0
- When using the cache credential helper, it could error out with "fatal: unable to connect to cache daemon: Unknown error" under certain circumstances; This was fixed.
- Git for Windows used to issue a misleading warning when .gitignore was a directory, which has been fixed.

Changes since Git for Windows v2.47.1 (November 25th 2024)
New Features
- Comes with Git Credential Manager v2.6.1, addressing CVE-2024-50338.
- Comes with Git LFS v3.6.1, addressing CVE-2024-53263.
Bug Fixes
- CVE-2024-50338: Git Credential Manager can be tricked to exfiltrate credentials for a trusted site to an untrusted site. Since the URLs needed for such an attack look suspicious, this usually requires a recursive clone or fetch.
- CVE-2024-53263: In conjunction with CVE-2024-52006, Git LFS can be tricked to exfiltrate credentials for a trusted site to an untrusted site.
- CVE-2024-50349: When prompting the user for a password in the terminal, Git does not neutralize control characters.
- CVE-2024-52005: The sideband channel does not neutralize control characters.
- CVE-2024-52006: Similar to CVE-2020-5260, affecting credential helpers that interpret Carriage Returns as newlines.

Changes since Git for Windows v2.47.0(2) (October 22nd 2024)
This release comes with the first early native support of Windows/ARM64, ready for testing. Please report any issues!
New Features
- Comes with Git v2.47.1.
- Comes with cURL v8.11.0.
- Comes with Git LFS v3.6.0.
Bug Fixes
- Due to a bug introduced in the v2.47 cycle, the installer showed an empty "experimental options" page, which was fixed.
- A potential crash in Git Bash on Insider versions of Windows/ARM64 was fixed.
- On Windows/ARM64, running the 64-bit version of Git for Windows could infrequently cause deadlocked threads (see e.g. this report or this one), which was addressed.

Changes since Git for Windows v2.47.0 (October 8th 2024)
Bug Fixes
- A regression in v2.47.0 where git maintenance start crashed immediately was fixed.
- A regression where clones, fetches and pushes via SSH would dead-lock was fixed.
- As of Git for Windows v2.47.0, Scalar was supposed to enable an optimized push algorithm, but for a typo didn't, which was fixed.
- A few documentation and other, minor bug fixes from upstream Git were integrated into Git for Windows early.

Changes since Git for Windows v2.46.2 (September 24th 2024)
Git for Windows for Windows v2.47 drops support for Windows 7 and for Windows 8, as announced previously.
Please also note that the 32-bit variant of Git for Windows is deprecated; Its last official release is planned for 2025.
New Features
- Comes with Git v2.47.0.
- Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.5.4, which drops Windows 7 and Windows 8 support.
- The new, experimental git backfill command was added: It helps fetching relevant Git objects smartly in a partial, sparse clone.
- The new, experimental git survey command was added. This command is designed to help identify less-than-ideal data shape in monorepos, and it will likely see highly active development. Stay tuned!
- Comes with Git Credential Manager v2.6.0.

Changes since Git for Windows v2.46.1 (September 18th 2024)
New Features
- Comes with Git v2.46.2.
- Comes with OpenSSH v9.9.P1.
- Comes with MinTTY v3.7.6.
- Comes with Bash v5.2.37.
- Comes with the new, experimental --full-name-hash option for git repack that helps packing monorepos more tightly.

Changes since Git for Windows v2.46.0 (July 29th 2024)
New Features
- Comes with Git v2.46.1.
- Comes with Bash v5.2.32.
- Comes with OpenSSL v3.2.3.
- Comes with MinTTY v3.7.5.
- Comes with cURL v8.10.1.
Bug Fixes
- The support code enabled via core.WSLCompat did not work well with files stored in subdirectories of the worktree, which has been fixed.
- When using an askpass helper (e.g. implicitly when running inside VS Code's internal terminal), Git v2.46.0 would error out with "read error: Invalid argument"; This bug has been fixed.

Changes since Git for Windows v2.45.2 (June 3rd 2024)
Git for Windows for Windows v2.46 is the last version to support for Windows 7 and for Windows 8, see MSYS2's corresponding deprecation announcement (Git for Windows relies on MSYS2 for components such as Bash and Perl).
Please also note that the 32-bit variant of Git for Windows is deprecated; Its last official release is planned for 2025.
New Features
- Comes with Git v2.46.0.
- Comes with OpenSSL v3.2.2.
- Comes with PCRE2 v10.44.
- Comes with OpenSSH v9.8.P1.
- Comes with Git Credential Manager v2.5.1.
- Comes with MinTTY v3.7.4.
- git config respects two user-wide configs: .gitconfig in the home directory, and .config/git/config. Since the latter isn't a Windows-native directory, Git for Windows now looks for Git/config in the AppData directory, unless .config/git/config exists.
- The FSMonitor feature is no longer experimental, and therefore no longer offered as installer option. Users are encouraged to enable this on a per-repository basis, via the config setting core.fsmonitor=true (scalar clone does this automatically).
- The server-side component of OpenSSH, which had been shipped with Git for Windows for historical reasons only, is now no longer distributed with it.
- Comes with cURL v8.9.0.
Bug Fixes
- Git Bash's ls command can now be used in OneDrive-managed folders without having to hydrate all the files.
- Git LFS v3.5.x and newer no longer support Windows 7. Instead of a helpful error message, it now simply crashes on that Windows version, leaving the user with the error message "panic before malloc heap initialized". This has been addressed: In addition to the unhelpful error message, Git is now saying what is going on and how to get out of the situation.
- As of v2.45.0, the manual pages of git clone and git init were broken, which has been fixed.

New Features
- Comes with Git v2.43.0.
- Comes with MSYS2 runtime v3.4.9.
- Comes with GNU TLS v3.8.1.
- When installing into a Windows setup with Mandatory Address Space Layout Randomization (ASLR) enabled, which is incompatible with the MSYS2 runtime powering Git Bash, SSH and some other programs distributed with Git for Windows, the Git for Windows installer now offers to add exceptions that will allow those programs to work as expected.
- Comes with OpenSSH v9.5.
P1.
- Comes with cURL v8.4.0.
- Comes with OpenSSL v3.1.4.
- Comes with Git Credential Manager v2.4.1.
- Comes with Bash v5.2.21.
- Comes with MinTTY v3.7.0.
Bug Fixes
- Symbolic links whose target is an absolute path _without_ the drive prefix accidentally had a drive prefix added when checked out, rendering them "eternally modified".
This bug has been fixed.
- Git for Windows's installer is no longer confused by global GIT_* environment variables.
- The installer no longer claims that "fast-forward or merge" is the default git pull behavior: The default behavior has changed in Git a while ago, to "fast-forward only".

Bug Fixes
- Git for Windows v2.42.0's release notes claimed that it ships with Git LFS v3.4.0, which is incorrect and has been fixed in this release.
- The installer option to enable support for Pseudo Consoles has been handled incorrectly since Git for Windows v2.41.0, which has been fixed.
- Some Git commands (those producing paged output, for example) experienced a significant slow-down under certain circumstances, when running on a machine joined to a domain controller, which has been fixed.
- As of Git for Windows v2.41.0, when installed into a location whose path contains non-ASCII characters, it was no longer possible to fetch from/push to remote repositories via https://, which has been fixed.

Bug Fixes
- Git for Windows v2.42.0's release notes claimed that it ships with Git LFS v3.4.0, which is incorrect and has been fixed in this release.
- The installer option to enable support for Pseudo Consoles has been handled incorrectly since Git for Windows v2.41.0, which has been fixed.
- Some Git commands (those producing paged output, for example) experienced a significant slow-down under certain circumstances, when running on a machine joined to a domain controller, which has been fixed.
- As of Git for Windows v2.41.0, when installed into a location whose path contains non-ASCII characters, it was no longer possible to fetch from/push to remote repositories via https://, which has been fixed.

New Features
- Comes with Git Credential Manager v2.2.2.

New Features
• Comes with Git v2.35.0.
• Comes with a version of the MSYS2 runtime (Git for Windows flavor) based on Cygwin 3.3.3.
• Comes with OpenSSL v1.1.1m.
• Comes with Git Credential Manager Core v2.0.632.34631.
• Comes with cURL v7.81.0.
• Comes with tig v2.5.5.
• Comes with patch level 4 of the MSYS2 runtime (Git for Windows flavor) based on Cygwin 3.3.3.

Bug Fixes
• A bug which caused crashes when running git log with custom date formats in 32-bit builds was fixed.