You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Dependency updates (#2483)
- Documentation updates for AI agents (#2469)
- Official release pipeline signing fixes, and update to use the new Mac
pool (#2467, #2468)
- Fix for Linux SecretService credential MIME type (#2475)
- Allow headless use of Linux SecretService (#2474)
Would be nice if this could be released soon, I am getting the following warning from Bitbucket upon push:
remote: You are using Git Credential Manager (GCM) to authenticate Git over HTTPs.
remote: The version you are using will be blocked by Bitbucket Cloud on November 30, 2026.
remote: Please upgrade to a version newer than v3.0.0 as soon as possible.
remote: For more details:
remote: https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-348
Git for Windows 2.98.0 is expected to be released a few days after December 21st. That's the next full release currently planed. There might be a 2.56.1 or 2.56.0(5) in the meantime, but I'm currently unaware of any plans for such an intermediate release.
The prerelease 2.98.0-rc0 will most likely be released in the first week of December.
Before that there will likely be a few snapshot builds. Any snapshot dated November should come with GCM 3.
Ok thanks for the etas, I will probably either look into installing a Pre-Release once Atlassian's deadline hits, or potentially see if I can circumvent this if I setup an SSH key or sth.
Git for Windows 2.98.0 is expected to be released a few days after December 21st. That's the next full release currently planed. There might be a 2.56.1 or 2.56.0(5) in the meantime, but I'm currently unaware of any plans for such an intermediate release.
The prerelease 2.98.0-rc0 will most likely be released in the first week of December.
Before that there will likely be a few snapshot builds. Any snapshot dated November should come with GCM 3.
@rimrul I noticed that today's release (2.56.1.windows.1) still seems to have GCM 2.9.1+6760f0ef069c994aa2bb1d703fb374986ee82a3e. Any chance I'm installing the wrong version?
@wdbsb v2.56.1 is a security bug-fix release. Any non-critical upgrade such as GCM must not be snuck into such a release. So yes, it still comes with GCM v2.9.1, and that's intentional. We cannot risk regressions to be introduced by non-critical updates when we need to get security fixes out to the users.
Activity
rimrul commentedon Oct 27, 2026
/open pr
The workflow run was started
rimrul commentedon Oct 27, 2026
We'll need to adjust the update script to account for a new lack of x86 binaries.
dscho commentedon Oct 27, 2026
Oh right! x86 will be stuck with GCM v2.x.
We could take a page out of MSYS2's book and add a
mingw-w64-git-credential-manager-2.6package. But then, we can cross that bridge when (if?) we need it, and simply add the linemingw_arch=('mingw64' 'ucrt64' 'clangarm64')to https://github.com/git-for-windows/build-extra/blob/HEAD/mingw-w64-git-credential-manager/PKGBUILD. Obviously we'll also want to adjust https://github.com/git-for-windows/git-for-windows-automation/blob/3a88b579cdcf0d8b243792034349693269390ae9/.github/workflows/build-and-deploy.yml#L252 to no longer includemingw32.rimrul commentedon Oct 27, 2026
Does any of our tooling actually care about
mingw_arch? I thought that was purely a MSYS2 autobuild thing.dscho commentedon Oct 28, 2026
@rimrul Hmm. I thought that this was a
makepkg-mingwthing, but it isn't... Sorry about the noise!rimrul commentedon Oct 28, 2026
/add relnote
The following deployment(s) are missing:
rimrul commentedon Oct 28, 2026
/add relnote
The following deployment(s) are missing:
dscho commentedon Oct 28, 2026
/add relnote
The workflow run was started
dtirschek commentedon Nov 2, 2026
Would be nice if this could be released soon, I am getting the following warning from Bitbucket upon push:
rimrul commentedon Nov 2, 2026
Git for Windows 2.98.0 is expected to be released a few days after December 21st. That's the next full release currently planed. There might be a 2.56.1 or 2.56.0(5) in the meantime, but I'm currently unaware of any plans for such an intermediate release.
The prerelease 2.98.0-rc0 will most likely be released in the first week of December.
Before that there will likely be a few snapshot builds. Any snapshot dated November should come with GCM 3.
dscho commentedon Nov 2, 2026
I concur with @rimrul, a new release (after the recent flurry of security bug fix releases) is not planned, to counter upgrade fatigue.
dtirschek commentedon Nov 2, 2026
Ok thanks for the etas, I will probably either look into installing a Pre-Release once Atlassian's deadline hits, or potentially see if I can circumvent this if I setup an SSH key or sth.
wdbsb commentedon Nov 10, 2026
@rimrul I noticed that today's release (2.56.1.windows.1) still seems to have GCM 2.9.1+6760f0ef069c994aa2bb1d703fb374986ee82a3e. Any chance I'm installing the wrong version?
dscho commentedon Nov 11, 2026
@wdbsb v2.56.1 is a security bug-fix release. Any non-critical upgrade such as GCM must not be snuck into such a release. So yes, it still comes with GCM v2.9.1, and that's intentional. We cannot risk regressions to be introduced by non-critical updates when we need to get security fixes out to the users.