Git for Windows v2.49.0-rc1.windows.1

[gitforwindowshelper[bot]]

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-rc1.
• 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.

Filename	SHA-256
Git-2.49.0-rc1-64-bit.exe	81bf3f20c85c0ca82de760da8ac28eec53523edfb24a7c71f925e1c1e11bbe40
Git-2.49.0-rc1-arm64.exe	1b527f8e80c10a09d561908fd8cbe8acefb47bd1f61da5048188808deed64183
PortableGit-2.49.0-rc1-64-bit.7z.exe	b387c7ae0ce0eb751e5ca812fd47dddc8b53f0cc1148b4ba67b66071e5933f1d
PortableGit-2.49.0-rc1-arm64.7z.exe	80a7a186150ff22b695e54b20e55684f6c1a6abeaf2f32c9c256263a8901465d
MinGit-2.49.0-rc1-64-bit.zip	bc0d31dcb8a04eb5b0645ef92f132c3e3b184817b3d840806c06accb51e47ef7
MinGit-2.49.0-rc1-arm64.zip	c0244edc063ccb23aa425c88a591d2e90e6967725e168070ca64aea55e78ebb1
MinGit-2.49.0-rc1-32-bit.zip	b7edc701e8b874bca635896e0e9653bf1be5f6098d7046120c9a1a9af2f7844f
MinGit-2.49.0-rc1-busybox-64-bit.zip	dbeef21bf998c8094a936180251b51731040fccd0fa414c68a37b475b2ecebea
MinGit-2.49.0-rc1-busybox-32-bit.zip	aa516fe9904c406c29d9f030e80bf17de08aae009124fffad0249afd669da756
Git-2.49.0-rc1-64-bit.tar.bz2	65c1104bda7fa199829967a3f941c482721b983ffdb1132e76d2282a0e3f8c01
Git-2.49.0-rc1-arm64.tar.bz2	528e9c6759f30367e2cac04231c141d7973240ed7212d521bd2495d25878736a

---

This discussion was created from the release Git for Windows v2.49.0-rc1.windows.1.

[becm]

@dscho can we get a new GCM 2.6.2 with OAuth token (single line logic flow inconsistency) fixes

• fix(bitbucket): detect expired OAuth credentials git-ecosystem/git-credential-manager#1812
• fix(generic): save new refresh_token value git-ecosystem/git-credential-manager#1838

for the final release?
They are kind of a deployment blocker for some (2nd one for myself).

My personal 😉 wish-list would of course also include

• fix(generic): check local token expiry git-ecosystem/git-credential-manager#1837

[dscho]

I have no say in how GCM is run, unfortunately.