Git for Windows v2.51.0.windows.1

[gitforwindowshelper[bot]]

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.

Filename	SHA-256
Git-2.51.0-64-bit.exe	843037416371600a7f289be8fe2b2224afe1c1bb0736bbab7b3ff393e6a7aaf2
Git-2.51.0-arm64.exe	739673a52a2ea5a3ac23ef1a74985647fd21a758e5e177fed2d995dd897a1600
PortableGit-2.51.0-64-bit.7z.exe	a09b275d51ed3e829128e04cf4168fb54896cf6234bb30fecb8dc96a2bd321fa
PortableGit-2.51.0-arm64.7z.exe	0aacd4edf0c1715334a18725a947584652e1b34bddab63ac3f4a82c9f7c78e38
MinGit-2.51.0-64-bit.zip	c2c955a21fa99889d83f485f24fa5d9a38fffc2d509d4022385510e11c26b250
MinGit-2.51.0-arm64.zip	b21755ccd10f71a37ec341ca9ac450cebee71bb1e70c0d88d90ddd6e5b16dfa4
MinGit-2.51.0-32-bit.zip	5a8f1cace31a817fa9fa3d18146e8b40a28fd365d48958976df93ae6f0bae077
MinGit-2.51.0-busybox-64-bit.zip	6b71de89d321310d1cc233565a10b06cabc65582e1c37bae47548c1fa323c878
MinGit-2.51.0-busybox-32-bit.zip	050fe76ece1b7762cd556bdbe242a979d5d769c2072db45e1cc888061552779c
Git-2.51.0-64-bit.tar.bz2	151bddf70e1115631e62bb05535b5e6726b3813e1f363953ad6b4e6697d96933
Git-2.51.0-arm64.tar.bz2	5c3bc6ca50ef6a7686832d2549e6e1b3b1060cf18322a2bbe064d4aec2f33904

---

This discussion was created from the release Git for Windows v2.51.0.windows.1.

[dscho]

Looks that the combination of #5838 and #5839, and potentially a backport of microsoft#796, would constitute enough bug-fix material to justify a new Git for Windows version. What do you think @rimrul @mjcheetham?

[dscho]

I should probably also include https://lore.kernel.org/git/20250924-jk-fix-no-index-path-with-slash-v1-1-6b2028c0de92@intel.com/ (which, surprisingly, did not receive any feedback suggesting sweeping changes).

[dscho]

I looked through the "What's cooking in git.git" email to see whether there are more regression fixes that should be included in a bug-fix release, and there are!

• pw/rebase-i-cleanup-fix
  "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.
• tc/last-modified-recursive-fix
  "git last-modified" operating in non-recursive mode used to trigger a BUG(), which has been corrected.
• cs/subtree-squash-split-fix
  "git subtree" (in contrib/) did not work correctly when splitting squashed subtrees, which has been improved.
• jk/add-i-color
  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.
• ds/sparse-checkout-clean
  "git sparse-checkout" subcommand learned a new "clean" action to prune otherwise unused working-tree files that are outside the areas of interest. (this corresponds to [2.51.0 Bug] Missing singleton objects in 'git repack -adf --path-walk' microsoft/git#796)

I omitted #5839, which is:

• kn/refs-files-case-insensitive
  Deal 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.

[dscho]

Looking through what's been merged to master and already dropped out of the "What's cooking in git.git" emails, I also see:

• sg/line-log-boundary-fixes
  A corner case bug in "git log -L..." has been corrected.
• ps/upload-pack-oom-protection
  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.
• ds/midx-write-fixes
  Fixes multiple crashes around midx write-out codepaths.
• ds/path-walk-repack-fix
  "git repack --path-walk" lost objects in some corner cases, which has been corrected.
• jk/fetch-check-graph-objects-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.
• ly/diff-name-only-with-diff-from-content
  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.
• jc/diff-no-index-in-subdir
  "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 cwd and prefix.
• en/ort-rename-fixes
  Various bugs about rename handling in "ort" merge strategy have been fixed.
• dl/push-missing-object-error
  "git push" had a code path that led to BUG() but it should have been a die(), as it is a response to a usual but invalid end-user action to attempt pushing an object that does not exist.
• ps/reflog-migrate-fixes
  "git refs migrate" to migrate the reflog entries from a refs backend to another had a handful of bugs squashed.
• js/rebase-i-allow-drop-on-a-merge
  During interactive rebase, using 'drop' on a merge commit lead to an error, which was incorrect.

[dscho]

See #5840 for the roll-up PR.

[dscho]

My current plan is to release Git for Windows v2.51.0(2) with all of these fixes on this coming Monday, September 29th 2025.

[dscho]

↦ #5844