Git for Windows v2.40.0
Changes since Git for Windows v2.39.2 (February 14th 2023)
As announced previously, Git for Windows will drop support for Windows
7 and for Windows 8 in one of the next versions, following Cygwin's and
MSYS2's lead (Git for Windows relies on MSYS2 for components such as
Bash and Perl).
Also following the footsteps of the MSYS2 and Cygwin projects on which
Git for Windows depends, the 32-bit variant of Git for Windows is
nearing its end of support.
New Features
* Comes with Git v2.40.0.
* In the olden Git days, there were "dashed" Git commands (e.g.
git-commit instead of git commit). These haven't been supported for
interactive use in a really, really long time. But they still
worked in Git aliases and hooks ("scripts"). Since Git v1.5.4
(released on February 2nd, 2008), it was discouraged/deprecated to
use dashed Git commands even in scripts. As of this version, Git
for Windows no longer supports these dashed commands.
* Comes with tig v2.5.8.
* Comes with Bash v5.2 patchlevel 15.
* Comes with OpenSSL v1.1.1t.
* Comes with GNU TLS v3.8.0.
* Comes with cURL v7.88.1.
* Comes with libfido2 v1.13.0.
* Comes with Git Credential Manager v2.0.935.
Bug Fixes
* Some commands mishandled absolute paths near the drive root (e.g.
scalar unregister C:/foo), which has been fixed.
* When trying to call Cygwin (or for that matter, MSYS2) programs
from Git Bash, users would frequently be greeted with cryptic error
messages about a "cygheap" or even just an even more puzzling exit
code 127. Many of these calls now succeed, allowing basic
interactions. While it is still not possible for, say, Cygwin's
vim.exe to interact with the Git Bash's terminal window, it is now
possible for Cygwin's zstd.exe in conjuction with Git for Windows'
tar.exe to handle .tar.zst archives.