git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: git@vger.kernel.org, git-packagers@googlegroups.com
Subject: [ANNOUNCE] Git for Windows 2.54.0-rc2
Date: Tue, 14 Apr 2026 22:35:08 +0200 (CEST)	[thread overview]
Message-ID: <1Ml6qC-1visl82M1c-00mU8M@mail.gmx.net> (raw)

Dear Git users,

I hereby announce that Git for Windows 2.54.0-rc2 is available from:

    https://github.com/git-for-windows/git/releases/tag/v2.54.0-rc2.windows.1

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-rc2.
  * Comes with Bash v5.3.9.
  * Comes with Git Credential Manager v2.7.2.
  * 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.

Git-2.54.0-rc2-64-bit.exe | de00b78d1a95511c5e80368fcf7b8ceeee487f9b00afc2fb44c05856343f9cdf
Git-2.54.0-rc2-arm64.exe | 8ec8e9b4dbe94517e7356e1f204c12564681a7edf9f315f5ffd52841036cf136
PortableGit-2.54.0-rc2-64-bit.7z.exe | d0109858c7da928c3251a01201a433722882809148045786dc4cddf092cd20e9
PortableGit-2.54.0-rc2-arm64.7z.exe | 66c613f18d190eee833a7a5e40d38ed95ac032a716fb3f094e0765cfe85b742a
MinGit-2.54.0-rc2-64-bit.zip | 684e11c6972b2c4718f4aa38cbfd420b635e0d0e52734ddb7da6e92862f04a67
MinGit-2.54.0-rc2-arm64.zip | e75b603b5627cc053497ac268b97d8caa21b2b7d2f7bb0121f7b64b183c41b73
MinGit-2.54.0-rc2-32-bit.zip | f3538df09a79dc005169225a65e80f8278052ffe4b4de97addbbecae61dd0969
MinGit-2.54.0-rc2-busybox-64-bit.zip | b1b9bcb9448a9815a01f0bca620223ad5d6f64654433f6062cbe1a8af84a59f6
MinGit-2.54.0-rc2-busybox-32-bit.zip | 752a774cace37345597ba6b4126e5c64a859f4b0f2eaf9a8c0edb08634c592e0
Git-2.54.0-rc2-64-bit.tar.bz2 | 8cb1d6f22563eb1b16ea8ad88525bdf9c4d700cc58cd8da6e7171dce694fa8b4
Git-2.54.0-rc2-arm64.tar.bz2 | 58ac72aa2c7d3d4c3535c8ffe61d139a0a795c348a0f11a7d80e5d39218b328a

Ciao,
Johannes


                 reply	other threads:[~2026-04-14 20:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1Ml6qC-1visl82M1c-00mU8M@mail.gmx.net \
    --to=johannes.schindelin@gmx.de \
    --cc=git-packagers@googlegroups.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).