Releases: git-for-windows/git-snapshots
Releases · git-for-windows/git-snapshots
Thu, May 22, 2025, 12:42:40 PM GMT
stop mentioning the old selfhosted arm64 runner setup (#5630) We don't use the selfhosted runners anymore, drop the outdated paragraph describing that old setup.
Thu, May 22, 2025, 06:20:49 AM GMT
monitor-components: skip curl prereleases (#5629) curl recently started releasing rc versions, but we don't want to act on them, so there is no need to open issues about every rc version.
Wed, Apr 30, 2025, 02:33:47 PM GMT
Fix t0060.221 on Windows/ARM64 (#5610) Apparently my tests of https://github.com/git-for-windows/git/pull/5586 had been incomplete. This here patch is needed to let t0060.221 pass (where it verifies that `git.exe` sets `MSYSTEM` correctly if that environment variable has not yet been set): Simply reverse the order of the tests whether to set `MINGW64` or `CLANGARM64` to avoid using the former on Windows/ARM64 by mistake.
Mon, Apr 21, 2025, 12:13:05 PM GMT
Upgrade to mimalloc v2.2.3 (#5508) Git for Windows still carries [mimalloc v2.1.2](https://github.com/microsoft/mimalloc/releases/tag/v2.1.2), which is almost 2 years old. Let's upgrade.
Mon, Apr 21, 2025, 11:34:38 AM GMT
clangarm64: let the tests pass! (#5586) I encountered these issues that had hitherto escaped us [when I worked on letting the `ci-artifacts` workflow in git-sdk-arm64 also build Git and run the test suite](https://github.com/git-for-windows/git-sdk-arm64/pull/37) by way of validating the `minimal-sdk` artifact. Mind, this PR does not only adjust a test case that was previously too fixated on x86_64. There are two real issues that this PR addresses and that were found via the test suite: - When the environment variable `MSYSTEM` is not yet set, it now is set appropriately even on Windows/ARM64 (and the `PATH` is adjusted accordingly). - The tree traversal limit designed to avoid stack overflows needed to be adjusted for the clangarm64 builds.
Wed, Apr 16, 2025, 02:11:10 PM GMT
Fix CI builds again (#5590) I noticed that the CI builds of `shears/main` were failing, as well as the PR builds of #5586. The reasons are outside of Git for Windows, but the fixes need to be inside anyway.
Mon, Apr 7, 2025, 06:50:10 AM GMT
fixup! mingw: support long paths (#5550) When rebasing c8b6c1db91d8 (mingw: support long paths, 2015-07-28) on top of 391bceae4350 (compat/mingw: support POSIX semantics for atomic renames, 2024-10-27) a newly introduced MAX_PATH buffer was not increased to MAX_LONG_PATH. This fixes https://github.com/git-for-windows/git/issues/5476
Wed, Mar 26, 2025, 12:21:47 PM GMT
mingw_rename: support ReFS on Windows 2022 (#5515) Git on Windows 2022 fails to write config files on ReFS with the error message "Function not implemented". The reason is that `ERROR_NOT_SUPPORTED` is reported (not `ERROR_INVALID_PARAMETER`, as expected). Let's handle both errors the same: by falling back to the best-effort option, namely to rename without POSIX semantics. This fixes https://github.com/git-for-windows/git/issues/5427
Wed, Mar 19, 2025, 12:37:11 PM GMT
Replace the superseded wiki URLs (#5495) This is a follow-up for https://github.com/git-for-windows/git-for-windows.github.io/pull/59.
Fri, Mar 14, 2025, 09:30:57 PM GMT
Merge 'readme' into HEAD Add a README.md for GitHub goodness. Signed-off-by: Johannes Schindelin <[email protected]>