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 communitys 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 Gits 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.

Git for Windows v2.47.1.windows.1 Latest$$$$$$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 (the included Git Bash is actually not native; for technical reasons; but the git is a native ARM64 executable). 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.

= Release 2.17.0.2 =$$$Released: 2024-11-01$$$$$$This is the last version that will work on Windows 7 and 8 (and possibly 8.1).$$$$$$The TortoiseGit 2.17.0.1 installer was missing statically linked x86 libraries for the x64 build.$$$$$$== Bug Fixes ==$$$ * Fixed issue #4177: TortoiseGit dialogs may not be visible (when a modal sub dialog is shown too early during dialog initialization)$$$ This reverts the fix for issue #4118: When dark mode is enabled; dialogs momentarily flicker with light mode UI elements on opening$$$$$$== Known issues ==$$$ * Issue #4013: Incorrect info displayed in title bar of Windows Explorer windows$$$ At the moment the numbers are only updated when the index or the current branch change.

Git for Windows v2.47.0.windows.2 Latest$$$$$$ v2.47.0.windows.2 $$$ 1f8a83c$$$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 didnt; which was fixed.$$$A few documentation and other; minor bug fixes from upstream Git were integrated into Git for Windows early.

Releases v2.47.0.windows.1$$$Git for Windows v2.47.0.windows.1 Latest$$$@gitforwindowshelper gitforwindowshelper released this yesterday$$$ v2.47.0.windows.1 $$$ d53e464$$$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.$$$Filenamet

Git for Windows v2.46.2.windows.1$$$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.

Git for Windows v2.46.1.windows.1 Latest$$$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 Codes internal terminal); Git v2.46.0 would error out with read error: Invalid argument; This bug has been fixed.

Git for Windows v2.46.0.windows.1 Latest$$$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 MSYS2s 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 isnt 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 Bashs 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.

Git for Windows v2.45.2.windows.1$$$New Features$$$Comes with Git v2.45.2.$$$Comes with Tig v2.5.10.$$$Comes with cURL v8.8.0.$$$Bug Fixes$$$When Git for Windows v2.44.0 introduced the ability to use native Win32 Console ANSI sequence processing; an inadvertent fallout was that in this instance; non-ASCII characters were no longer printed correctly unless the current code page was set to 65001. This bug has been fixed.

Git for Windows v2.45.1 Latest$$$@dscho dscho released this 2 days ago$$$· 5 commits to main since this release$$$ v2.45.1.windows.1 $$$ 965b167$$$Changes since Git for Windows v2.45.0 (April 29th 2024)$$$$$$Git for Windows for Windows v2.45 is the last version to support for Windows 7 and for Windows 8; see MSYS2s 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.45.1.$$$Bug Fixes$$$CVE-2024-32002: Recursive clones on case-insensitive filesystems that support$$$symbolic links are susceptible to case confusion that can be exploited to$$$execute just-cloned code during the clone operation.$$$CVE-2024-32004: Repositories can be configured to execute arbitrary code$$$during local clones. To address this; the ownership checks introduced in$$$v2.30.3 are now extended to cover cloning local repositories.$$$CVE-2024-32020: Local clones may end up hardlinking files into the target$$$repositorys object database when source and target repository reside on the$$$same disk. If the source repository is owned by a different user; then those$$$hardlinked files may be rewritten at any point in time by the untrusted user.$$$CVE-2024-32021: When cloning a local source repository that contains symlinks$$$via the filesystem; Git may create hardlinks to arbitrary user-readable files$$$on the same filesystem as the target repository in the objects/ directory.$$$CVE-2024-32465: It is supposed to be safe to clone untrusted repositories;$$$even those unpacked from zip archives or tarballs originating from untrusted$$$sources; but Git can be tricked to run arbitrary code as part of the clone.$$$Defense-in-depth: submodule: require the submodule path to contain$$$directories only.$$$Defense-in-depth: clone: when symbolic links collide with directories; keep$$$the latter.$$$Defense-in-depth: clone: prevent hooks from running during a clone.$$$Defense-in-depth: core.hooksPath: add some protection while cloning.$$$Defense-in-depth: fsck: warn about symlink pointing inside a gitdir.$$$Various fix-ups on HTTP tests.$$$HTTP Header redaction code has been adjusted for a newer version of cURL$$$library that shows its traces differently from earlier versions.$$$Fix was added to work around a regression in libcURL 8.7.0 (which has already$$$been fixed in their tip of the tree).$$$Replace macos-12 used at GitHub CI with macos-13.$$$ci(linux-asan/linux-ubsan): lets save some time$$$Tests with LSan from time to time seem to emit harmless message that makes$$$our tests unnecessarily flakey; we work it around by filtering the$$$uninteresting output.$$$Update GitHub Actions jobs to avoid warnings against using deprecated version$$$of Node.js.

Release 2.16.0 =$$$Released: 2024-04-30$$$$$$Support for Windows 7 and 8 will be dropped with one of the next releases.$$$$$$Contains a fix for a critical vulnerability (CVE-2024-31497) in PuTTY with 521-bit ECDSA keys; see notes for release 2.15.0.1.$$$$$$== Features ==$$$ * Updated OGDF to 2023.09 (Elderberry)$$$ * Update Scintilla to 5.5.0 and Lexilla to 5.3.2$$$ * Updated zlib to 1.3.1$$$ * TortoiseGitMerge: Add ignore line endings button to Ribbon$$$ * Allow BugTraq Select issue-button at the same time as the textbox$$$ * Add support for GIT_TEMPLATE_DIR environment variable$$$ * Updated libgit to 2.43 based on Git for Windows sources$$$ * Updated libgit2 to 1.8.0$$$ libgit2 now supports worktree config$$$ * Updated pcre2 to 10.43$$$ * Update json library to 3.11.3$$$ * Update editorconfig to 0.12.7$$$ * Fixed issue #3881: Compare Revisions - Revert - can not undo an Add action$$$ * Fixed issue #4097: Revert to parent version menu missing for added files in Log Viewer$$$ * Fixed issue #4112: After conducting a hard reset; git clean should be offered$$$ * Fixed issue #3325: Display repository name first in window title$$$ Can be controlled using the DialogTitles advanced setting.$$$ * Fixed issue #3981: Add stash controls to the Switch/Checkout progress dialog$$$ * Fixed issue #4015: Add --force option for worktree remove$$$$$$== Bug Fixes ==$$$ * Fixed issue #4085: ImportPatch is closing even click NO$$$ * Fixed issue #4082: TortoiseGitMerge: Particular usage undo/redo function casue exception/freeze window$$$ * Fixed issue #4086: ResolveDlg: Merge conflict file gets changed after fixing merge and pressing Resolve$$$ * Fixed issue #3917: Git not getting LFS files (SSHAskPass not showing)$$$ * Fixed issue #4083: TortoiseGitMerge: Infinite loop when diff file has only 1 line and perform Redo$$$ * Sanitize GIT_* environment variables to prevent passing environment variables to git that are currently unsupported in TortoiseGit/libgit2 to prevent inconsistencies$$$ * Fixed issue #4096: Git configuration under XDG_CONFIG_HOME is not recognized correctly$$$ * TortoiseGitBlame: Fix blaming a file from another working tree$$$ * Fixed issue #4073: TortoiseGit extremely slow on network shares / UNC paths since 2.14$$$ * Fixed issue #4106: Submodule Update with force not working when using the Git Sync Dialog$$$ * Fixed issue #4110: TortoiseGitMerge: Ribbon becomes empty after maximizing on Windows 11$$$ * Fixed issue #4004: TortoiseGit closes window after commit when pressing push when the owning explorer window has been closed$$$ * Fixed issue #3909: App freezes when pasting from a closed logs window$$$ * Fixed issue #3959: The slash direction of the abbreviated path displayed in the dialog box is different$$$ * Fixed issue #4122: TortoiseGitMerge Encountered an improper argument error message$$$$$$== Known issues ==$$$ * Issue #4013: Incorrect info displayed in title bar of Windows Explorer windows$$$ At the moment the numbers are only updated when the index or the current branch change.

Git for Windows v2.45.0.windows.1 Latest$$$Changes since Git for Windows v2.44.0 (February 23rd 2024)$$$$$$Git for Windows for Windows v2.45 is the last version to support for Windows 7 and for Windows 8; see MSYS2s 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.45.0.$$$Comes with PCRE2 v10.43.$$$Comes with GNU Privacy Guard v2.4.5.$$$Comes with Git LFS v3.5.1.$$$MinGit now supports running git difftool.$$$Comes with OpenSSH v9.7.P1.$$$Comes with GNU TLS v3.8.4.$$$Comes with Tig v2.5.9.$$$Comes with cURL v8.7.1.$$$Comes with Git Credential Manager v2.5.0.$$$Bug Fixes$$$Since v2.14.0(2); Git for Windows installer registers the Open Git Bash here and Open Git GUI here context menu items also in the special Libraries folders; but the uninstaller never removed them from those folders; which was fixed.$$$A regression where git clone no longer worked in the presence of includeIf.*.onbranch config settings has been fixed.$$$Apparently some anti-malware programs fiddle with the mode of stdout which can lead to problems because expected output is missing; which was fixed.

Changes since Git for Windows v2.43.0 (November 20th 2023)$$$$$$Git for Windows for Windows v2.44 is the last version to support for Windows 7 and for Windows 8; see MSYS2s 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.44.0.$$$Comes with libfido2 v1.14.0.$$$Comes with the MSYS2 runtime (Git for Windows flavor) based on Cygwin v3.4.10.$$$Comes with Perl v5.38.2.$$$Git for Windows learned to detect and use native Windows support for ANSI sequences; which allows using 24-bit colors in terminal windows.$$$Comes with Git LFS v3.4.1.$$$The repository viewer Tig that is included in Git for Windows can now be called also directly from PowerShell/CMD.$$$Comes with OpenSSH v9.6.P1.$$$Comes with Bash v5.2.26.$$$Comes with GNU TLS v3.8.3.$$$Comes with OpenSSL v3.2.1.$$$Comes with cURL v8.6.0.$$$Comes with GNU Privacy Guard v2.4.4.$$$Bug Fixes$$$The 32-bit variant of Git for Windows was missing some MSYS2 runtime updates; which was addressed; Do note 32-bit support is phased out.$$$The Git for Windows installer showed cut-off text in some setups. This has been fixed.$$$The git credential-manager --help command previously would not find a page to display in the web browser; which has been fixed.$$$A couple of bugs that could cause Git Bash to hang in certain scenarios were fixed.

Git for Windows v2.43.0.windows.1$$$$$$Changes since Git for Windows v2.42.0(2) (August 30th 2023)$$$$$$As announced previously; Git for Windows will drop support for Windows 7 and for Windows 8 in one of the next versions; following Cygwins and MSYS2s lead (Git for Windows relies on MSYS2 for components such as Bash and Perl).$$$$$$Following the footsteps of the MSYS2 and Cygwin projects on which Git for Windows depends; the 32-bit variant of Git for Windows is being phased out.$$$$$$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 Windowss 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.

= Release 2.15.0 =$$$Released: 2023-10-03$$$$$$Support for Windows 7 and 8 will be dropped with one of the next releases.$$$$$$== Features ==$$$ * Fixed issue #4027: Autocompletion doesnt handle JS classes$$$ * Updated libapr to 1.7.4$$$ * Updated libapr-util to 1.6.3$$$ * Updated pcre2 to 10.42$$$ * Updated libgit to 2.40.1 based on Git for Windows sources$$$ * Updated libgit2 to 1.7.1$$$ * Updated zlib to 1.3$$$ * Update TortoiseGitPlink to PuTTY Plink 0.79$$$ * Update shipped PuTTY binaries to 0.79$$$ * Fixed issue #3974: Windows 11 Context Menus only display in single user when has multiple users$$$ Added a button to register the win11 context menu for the current user in TortoiseGit settings on the Windows 11 contextmenu page$$$ * Update Scintilla to 5.3.6 and Lexilla to 5.2.7$$$ * Fixed issue #3435: Dramatically speed up revert operations$$$ * Fixed issue #3053: Abort button in merge conflict dialogue is misleading -> opens Abort merge dialog now$$$ * Fixed issue #4034: After git lfs lock; UI suggest a pull$$$ * Allow the dark mode to be always enabled if possible (e.g.; using Ctrl+Alt+D)$$$ * Add support for SVG files in TortoiseGitIDiff$$$ * Fixed issue #4033: Add workaround for broken scoop shim$$$ * Lots of refactorings and performance optimizations$$$ * Fixed issue #4040: TortoiseGitBlame: Ability to select multiple commits (line highlighting)$$$ * Make TortoiseGitMerge and SSHAskPass multi-monitor DPI aware$$$ * Fixed issue #3698: Resolve conflict using theirs is extremely slow $$$ * Update editorconfig to 0.12.6$$$ * Fixed issue #3745: Support show log for both A..B and B..A$$$ * Fixed issue #2754: Add hint for pressing F5 for Refresh in TortoiseGit Commit window$$$$$$== Bug Fixes ==$$$ * Fixed redraw bug in log list$$$ * Fixed issue #3843: Revert does not work for submodules$$$ * Fixed issue #4030: TortoiseGitMerge Dark mode flashes white when opening$$$ * Fixed issue #4041: Git Worktree Add command error 129 when directory path contains spaces$$$ * Improved Cygwin and Msys2 compatibility$$$ * TortoiseGitMerge: Fixed optical glitch if wrap mode is enabled with non-ASCII files$$$ * Fixed issue #4049: Diff with previous version - ENTER closes dialog$$$ * Fixed issue #4051: Copy ref names in nested view does not copy full ref name$$$ * Fixed issue #3373: Refresh log after shallow clone depth update$$$ * Improve crash resistance in log dialog on broken repositories$$$ * Fixed issue #4057: Clean up fails to delete files with Unicode characters in name if core.quotepath is not explicitly set$$$ * Fixed issue #4058: Performance issue when the Git index contains a large number of files$$$ * Fixed issue #3874: TortoiseGitMerge GUI elements overlap with Ribbon on Windows 7$$$$$$== Known issues ==$$$ * Issue #4013: Incorrect info displayed in title bar of Windows Explorer windows$$$ At the moment the numbers are only updated when the index or the current branch change.$$$

Changes since Git for Windows v2.42.0 (August 21st 2023)$$$$$$As announced previously; Git for Windows will drop support for Windows 7 and for Windows 8 in one of the next versions; following Cygwins and MSYS2s lead (Git for Windows relies on MSYS2 for components such as Bash and Perl).$$$$$$Following the footsteps of the MSYS2 and Cygwin projects on which Git for Windows depends; the 32-bit variant of Git for Windows is being phased out.$$$$$$Bug Fixes$$$Git for Windows v2.42.0s 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.

Changes since Git for Windows v2.41.0(2) (July 7th 2023)$$$$$$As announced previously; Git for Windows will drop support for Windows 7 and for Windows 8 in one of the next versions; following Cygwins and MSYS2s lead (Git for Windows relies on MSYS2 for components such as Bash and Perl).$$$$$$Following the footsteps of the MSYS2 and Cygwin projects on which Git for Windows depends; the 32-bit variant of Git for Windows is being phased out. As of Git for Windows v2.41.0; the 32-bit variant of the POSIX emulation layer (known as MSYS2 runtime; powering Git Bash among other components shipped with Git for Windows) is in maintenance mode and will only see security bug fixes (if any). Users relying on 32-bit Git for Windows are highly encouraged to switch to the 64-bit version whenever possible.$$$$$$This release is a hot-fix release to incorporate a new Git Credential Manager version that addresses several issues present in the previous verison. There are no other changes.

Changes since Git for Windows v2.40.0 (March 14th 2023)$$$$$$This is a security release; addressing CVE-2023-29012; CVE-2023-29011; CVE-2023-29007; CVE-2023-25815 and CVE-2023-25652.$$$$$$As announced previously; Git for Windows will drop support for Windows 7 and for Windows 8 in one of the next versions; following Cygwins and MSYS2s 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.1.$$$Bug Fixes$$$Addresses CVE-2023-29012; a vulnerability where starting Git CMD would execute doskey in the current directory; if it exists.$$$Addresses CVE-2023-29011; a vulnerability where the SOCKS5 proxy called connect is susceptible to picking up an untrusted configuration on multi-user machines.$$$Addresses CVE-2023-29007; a vulnerability where git submodule deinit can inadvertently introduce malicious changes into the Git config file.$$$Addresses CVE-2023-25815; a vulnerability where Git can unexpectedly show crafted localized messages written by another user on a multi-user machine.$$$Addresses CVE-2023-25652; a vulnerability where git apply --reject could follow symbolic links to write files outside the worktree.

= Release 2.14.0.1 =$$$Released: 2023-04-15$$$$$$== Bug Fixes ==$$$ * Fixed issue #3997: TortoiseGit crashes with libgit2 returned: failed to get security information: Incorrect function.

Git for Windows v2.40.0.windows.1 Latest$$$@gitforwindowshelper gitforwindowshelper released this 3 days ago$$$ v2.40.0.windows.1 $$$ 1d90ca2$$$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 Cygwins and MSYS2s 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 havent 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; Cygwins vim to interact with the Git Bashs terminal window; it is now possible for Cygwins zstd in conjuction with Git for Windows tar to handle .tar.zst archives.

= Release 2.14.0 =$$$Released: 2023-02-05$$$$$$== Features ==$$$ * Fixed issue #3860: Highlight keywords; such as error; fatal and warning in output of git commands$$$ * Update Scintilla to 5.3.2 and Lexilla to 5.2.1$$$ * Allow to see diff to previous commit on commit dialog for merge commits$$$ * Update libgit to 2.37.5 based on Git for Windows sources$$$ * Update libgit2 to 1.5.0$$$ * Update OGDF to version 2022.02$$$ * Fixed issue #3873: Submodule Add Dialog does not automatically grab the Git Clone link from the clipboard$$$ * Update zlib to 1.2.13$$$ * Update pcre2 to 10.40$$$ * Update hunspell to 1.7.2$$$ * LogDlg: Prevent the graph from drawing an unfinished line for each ignored parent on first-parent only walk$$$ * Update shipped PuTTY binaries to 0.78$$$ * Update TortoiseGitPlink to PuTTY Plink 0.78$$$ * Update TortoiseOverlays to 1.1.5$$$ * Fixed issue #3932: RebaseDlg: Remember last selection of add cherry picked from$$$ * Fixed issue #3938: Add Switch/Checkout... option after fetch$$$ * Fixed issue #3935: Submodule update is slow for repositories with several submodules$$$ * Fixed issue #3797: Add additional information to the Windows Explorer title$$$ * Fixed issue #3937: Support worktree operations (Add; remove; lock; unlock; prune) and worktree list$$$ Worktrees can also be created by dragndrop of a repository root directory$$$ * Fixed issue #3903: Wrong (empty) icon in Windows 11 taskbar$$$ * Fixed issue #3867: GitLog does not show super project pointers in conflicted submodule$$$ * Fixed issue #3789: Commit dialog: Amend Last Commit in Message section unclear$$$ * Fixed issue #3958: Pasting a path in the input box should automatically trim the quotes$$$ * Improved parsing Git URLs/branch names from clipboard for push/pull/fetch dialgos$$$ * CommitDlg: Allow to see diff to previous commit also for merge commits$$$ * Add special environment variable TGIT_INITIATED_CALL to indicate that a git call was issued from TortoiseGit$$$ * Add initial support for ARM64 (with separate MSI installer)$$$ * Fixed issue #3996: Improve compatibility with Win32-OpenSSH (Git hanging on waiting passphrase from stdin)$$$ * Fixed issue #3994: LogDlg: Allow to open new log dialog$$$$$$== Bug Fixes ==$$$ * Fixed issue #3865: Ampersand in branch name not shown in Windows context menu$$$ * Fixed issue #3868: 2.13 has bug for clone without checkout$$$ * Fixed issue #3863: Push... menu item in the log window context menu does not honor last selection of pushing all branches$$$ * Fixed issue #3870: Dialog after Bisect reset offers bisect step options$$$ * Removed right anchor from Staging Support checkbox on commit dialog$$$ * Fixed issue #3905: TortoiseGitMerge doesnt apply Settings/Colors/Misc/Whitespaces$$$ * Fixed issue #3900: Adjust min. height of Log Message dialog$$$ * Fixed issue #3929: commit window handles double-click strangely$$$ * Fixed issue #3926: TortoiseGitMerge undo/redo can cause window to become unresponsive$$$ * Fixed issue #3930: TortoiseGitMerge optimized docking PatchFileView$$$ * Fixed issue #3927: Support deleted files for Compare two files$$$ * Fixed issue #3911: TortoiseGitMerge: The text is identical ... dialog causes display issues$$$ * Fixed issue #3940: restore scroll position of list$$$ * Fixed issue #3906: Pull dialog always defaults to the wrong branch in submodules$$$ * Fixed issue #3897: Bisect refs are incorrect when working with worktrees$$$ * Fixed issue #3952: Log window wrong branch after cherry pick if switched after log window brought up$$$ * Fixed issue #3953: Disabling ShowListFullPathTooltip doesnt hide tooltips in Changed Files dialog$$$ * Fixed issue #3945: Combine to one commit sometimes broken$$$ * Fixed issue #3663: Wrong window has focus after pull$$$ * Fixed issue #3956: Sometimes rebase contains wrong list of files$$$ * LogDlg: Prevent the graph from drawing an unfinished line for each ignored parent on first-parent only walk$$$ * Start TGit processes without identity from the shell extension$$$

Git v2.39 Release Notes$$$=======================$$$$$$UI; Workflows & Features$$$------------------------$$$$$$ * git grep learned to expand the sparse-index more lazily and on$$$ demand in a sparse checkout.$$$$$$ * By default; use of fsmonitor on a repository on networked$$$ filesystem is disabled. Add knobs to make it workable on macOS.$$$$$$ * After checking out a branch that is a symbolic-ref that points at$$$ another branch; git symbolic-ref HEAD reports the underlying$$$ branch; not the symbolic-ref the user gave checkout as argument.$$$ The command learned the --no-recurse option to stop after$$$ dereferencing a symbolic-ref only once.$$$$$$ * git branch --edit-description @{-1} is now a way to edit branch$$$ description of the branch you were on before switching to the$$$ current branch.$$$$$$ * git merge-tree --stdin is a new way to request a series of merges$$$ and report the merge results.$$$$$$ * git shortlog learned to group by the format string.$$$

Git v2.38.1 Release Notes$$$=========================$$$$$$This release merges the security fix that appears in v2.30.6 (The CVEs are reserved; hence no CVE score available)$$$see the release notes for that version for details.$$$$$$Refer the 2.30.6 release notes$$$https://github.com/git/git/blob/master/Documentation/RelNotes/2.30.6.txt

Git v2.38 Release Notes$$$=======================$$$$$$UI; Workflows & Features$$$$$$ * git remote show [-n] frotz now pays attention to negative$$$ pathspec.$$$$$$ * git push sometimes performs poorly when reachability bitmaps are$$$ used; even in a repository where other operations are helped by$$$ bitmaps. The push.useBitmaps configuration variable is introduced$$$ to allow disabling use of reachability bitmaps only for git push.$$$$$$ * git grep -m<max-hits> is a way to limit the hits shown per file.$$$$$$ * git merge-tree learned a new mode where it takes two commits and$$$ computes a tree that would result in the merge commit; if the$$$ histories leading to these two commits were to be merged.$$$$$$ * git mv A B in a sparsely populated working tree can be asked to$$$ move a path between directories that are in cone (i.e. expected$$$ to be materialized in the working tree) and out of cone$$$ (i.e. expected to be hidden). The handling of such cases has been$$$ improved.$$$$$$ * Earlier; HTTP transport clients learned to tell the server side$$$ what locale they are in by sending Accept-Language HTTP header; but$$$ this was done only for some requests but not others.$$$$$$ * Introduce a safe.barerepository configuration variable that$$$ allows users to forbid discovery of bare repositories.$$$$$$ * Various messages that come from the pack-bitmap codepaths have been$$$ tweaked.$$$$$$ * git rebase -i learns to update branches whose tip appear in the$$$ rebased range with --update-refs option.$$$$$$ * git ls-files learns the --format option to tweak its output.$$$$$$ * git cat-file learned an option to use the mailmap when showing$$$ commit and tag objects.$$$$$$ * When git merge finds that it cannot perform a merge; it should$$$ restore the working tree to the state before the command was$$$ initiated; but in some corner cases it didnt.$$$$$$ * Operating modes like --batch of git cat-file command learned to$$$ take NUL-terminated input; instead of one-item-per-line.$$$$$$ * git rm has become more aware of the sparse-index feature.$$$$$$ * git rev-list --disk-usage learned to take an optional value$$$ human to show the reported value in human-readable format; like$$$ 3.40MiB.$$$$$$ * The diagnose feature to create a zip archive for diagnostic$$$ material has been lifted from scalar and made into a feature of$$$ git bugreport.$$$$$$ * The namespaces used by log --decorate from refs/ hierarchy by$$$ default has been tightened.$$$$$$ * git rev-list --ancestry-path=C A..B is a natural extension of$$$ git rev-list A..B; instead of choosing a subset of A..B to those$$$ that have ancestry relationship with A; it lets a subset with$$$ ancestry relationship with C.$$$$$$ * scalar now enables built-in fsmonitor on enlisted repositories;$$$ when able.$$$$$$ * The bash prompt (in contrib/) learned to optionally indicate when$$$ the index is unmerged.$$$$$$ * git clone command learned the --bundle-uri option to coordinate$$$ with hosting sites the use of pre-prepared bundle files.$$$$$$ * git range-diff learned to honor pathspec argument if given.$$$$$$ * git format-patch --from=<ident> can be told to add an in-body$$$ From: line even for commits that are authored by the given$$$ <ident> with --force-in-body-from option.$$$$$$ * The built-in fsmonitor refuses to work on a network mounted$$$ repositories; a configuration knob for users to override this has$$$ been introduced.$$$$$$ * The scalar addition from Microsoft is now part of the core Git$$$ installation.$$$$$$$$$Performance; Internal Implementation; Development Support etc.$$$$$$ * Collection of what is referenced by objects in promisor packs have$$$ been optimized to inspect these objects in the in-pack order.$$$$$$ * Introduce a helper to see if a branch is already being worked on$$$ (hence should not be newly checked out in a working tree); which$$$ performs mu

Git 2.37.3 Release Notes$$$========================$$$$$$This primarily is to backport various fixes accumulated on the master$$$front since 2.37.2.$$$$$$Fixes since v2.37.2$$$-------------------$$$$$$ * The build procedure for Windows that uses CMake has been updated to$$$ pick up the shell interpreter from local installation location.$$$$$$ * Conditionally allow building Python interpreter on Windows$$$$$$ * Fix to lstat() emulation on Windows.$$$$$$ * Older gcc with -Wall complains about the universal zero initializer$$$ struct s = { 0 }; idiom; which makes developers lives$$$ inconvenient (as -Werror is enabled by DEVELOPER=YesPlease). The$$$ build procedure has been tweaked to help these compilers.$$$$$$ * Plug memory leaks in the failure code path in the merge-ort merge$$$ strategy backend.$$$$$$ * Avoid repeatedly running getconf to ask libc version in the test$$$ suite; and instead just as it once per script.$$$$$$ * Platform-specific code that determines if a directory is OK to use$$$ as a repository has been taught to report more details; especially$$$ on Windows.$$$$$$ * vimdiff3 regression has been corrected.$$$$$$ * git fsck reads mode from tree objects but canonicalizes the mode$$$ before passing it to the logic to check object sanity; which has$$$ hid broken tree objects from the checking logic. This has been$$$ corrected; but to help exiting projects with broken tree objects$$$ that they cannot fix retroactively; the severity of anomalies this$$$ code detects has been demoted to info for now.$$$$$$ * Fixes to sparse index compatibility work for reset and checkout$$$ commands.$$$$$$ * Documentation for git add --renormalize has been improved.$$$$$$Also contains other minor documentation updates and code clean-ups.

New Features$$$Comes with Git v2.37.2.$$$Comes with tig v2.5.6.$$$Comes with Bash v5.1 patchlevel 016 .$$$Comes with Perl v5.36.0.$$$Gits executables are now marked Terminal Server-aware; meaning: Git will be slightly faster when being run using Remote Desktop Services.$$$git svn is now based on subversion v1.14.2.$$$Comes with GNU TLS v3.7.7.$$$Bug Fixes$$$Git for Windows now ships without the zmore and bzmore utilities (which were broken and included only inadvertently).$$$A regression in the vimdiff mode of git mergetool has been fixed.$$$With certain network drives; it was reported that some attributes associated with caching confused Git for Windows. This was fixed.

= Release 2.13.0.1 =$$$Released: 2022-02-06$$$$$$== Bug Fixes ==$$$ * Fixed issue #3856: Documentation Problem - Rebase needs more info and accurate info for setting upstream from CLI$$$ * Fixed issue #3855: Shell integration broken after upgrade to 2.13 (on Windows < 10)$$$ * Fixed issue #3859: Incorrect count of removed files if some files do not exist$$$ * Fixed issue #3857: Log Messages filter breaks Russian characters on pasting$$$

Release 2.13.0 =$$$Released: 2022-01-31$$$$$$== Changes ==$$$ * Git (for Windows) 2.24 or newer is now required$$$$$$== Features ==$$$ * Update Scintilla and Lexilla to 5.1.0$$$ * Fixed issue #3744: Update TortoiseGitPlink to PuTTY 0.76 and shipped binaries to PuTTY 0.76$$$ * Fixed issue #2379: Show changes as unified diff from Commit window on N files opens N diff windows$$$ * Fixed issue #3738: Added force flag on LFSLocksDlg$$$ * Fixed issue #2299: Better support the git staging process$$$ * Update libgit2 to 1.3.0$$$ * Update pcre2 to 10.39$$$ * Update editorconfig to 0.12.5$$$ * Update libgit to 2.32.0 based on Git for Windows sources$$$ * Fixed issue #3764: Add TortoiseGit menu to the right click menu in Windows 11$$$ * Fixed issue #3818: Change icon image for Cherry-Pick$$$ * Fixed issue #3728: Log Browser: Add an option to switch on full history (--full-history)$$$ * Fixed issue #2562: Automatically track remote when pushing untracked branch$$$ * Add support for Ctrl+A in BrowseRefsDlg and RepositoryBrowser$$$ * Fixed issue #3820: Stash changes should not offer stash pop/apply after no changes were stashed$$$ * Fixed issue #3812: Extend `:rebase` command with additional parameters$$$ * Fixed issue #3702: Push all branches should be unchecked when Push command is issued with a specific branch$$$ * Allow to keep changelists after committing$$$ * Fixed issue #3602: Make it possible to select multiple old commit messages from log history$$$ * Fixed issue #3782: Stash window may operate on unwanted stash under some circumstances when view is not refreshed$$$ * Fixed issue #3661: Exit code of TortoiseGitMerge should be based on success of a merge resolution$$$ * Fixed issue #3741: In `Browse Refs` show `gone` for branches tracking remote branches that have been deleted$$$ * TortoiseGitMerge: Correctly handle BOM changes to files when applying patches$$$ * Fixed issue #3787: Implement expanding/collapsing nodes in the log tree on demand$$$ * Fixed issue #3692: 64-bit version should bundle 64-bit pageant (and maybe other PuTTY binaries)$$$$$$== Bug Fixes ==$$$ * Fixed issue #3736: LFS force unlock not working$$$ * Fixed issue #3740: Setting DownloadAnimation=false has no effect; the turtle still flies$$$ * Remove extra space in front of Log Messages when drawing labels on right side$$$ * Fixed issue #3750: Dramatic speedup saving of large files from TortoiseMerge$$$ * Fixed issue #3781: TortoiseGitMerge Redo is not recorded as change$$$ * Fixed issue #3794: Submodules option is truncated in the Clean up dialog$$$ * Fixed issue #3813: Filter is checking for % incorrectly$$$ * Fixed issue #3779: Show branches this commit is on (References commit is on window) takes a very long time to find branches and tags$$$ * Fixed issue #3808: LFS stopped working (maybe related to major upgrade of git-lfs 3.x)$$$ * Fixed issue #3822: Crash (0xc0000409) in TortoiseGitProc when invoking git log$$$ * Fixes issue #3826: Help links to TortoiseGit site dont open in a sensible browser$$$ * Fixed issue #3815: TortoiseGitMerge crashes on Windows 7 on startup when winrt libraries are installed$$$ * Fixed issue #3831: TortoiseGitMerge omits text after null byte when word wrap is enabled$$$ * Fixed issue #3799: Display of Long lines with Chinese characters is truncated in TortoiseGitMerge dialog$$$ * Fixed issue #3836: TortoiseGitMerge: With line wrapping enabled; show the current column as in the wrapped line; not as the visible column$$$ * Fixed issue #3837: TortoiseGitMerge support link is outdated$$$ * Fixed issue #3834: Log window hangs on pasting wrong SHA-1 into commit log list when working tree changes are selected$$$ * Fixed issue #3793: Diff with previous version dialog does not clear files list during validation / for invalid version$$$ * Fixed issue #3784: Rebase dialog does not ask to pop stash when post rebase options in the lower left are used$$$ * Fixed issue #3625: Commit dialog shows wrong branch after committing failed when new branch was spec