Smells like a bug to me, but apparently I can't report one because I'm on free tier.
Been getting this warning lately:
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.
Fair enough, so I updated to the latest git credentials manager for windows, which is 3.0.2 (came out 12 days ago). And look what happens now:
git push
// TRACE REDACTED FOR SECURITY, IMPORTANT LINE HERE:
23:31:54.118258 run-command.c:673 trace: run_command: 'C:/Users/<username redacted>/AppData/Local/Programs/Git\ Credential\ Manager/git-credential-manager.exe store'
// FURTHER TRACE REDACTED
Enumerating objects: 13, done.
Counting objects: 100% (13/13), done.
Delta compression using up to 16 threads
Compressing objects: 100% (6/6), done.
Writing objects: 100% (7/7), 570 bytes | 570.00 KiB/s, done.
Total 7 (delta 4), reused 0 (delta 0), pack-reused 0 (from 0)
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.
So, still same warning. Confirmation that 3.0.2 is installed:
& "$env:LOCALAPPDATA\Programs\Git Credential Manager\git-credential-manager.exe" --version
23:36:52.672466 exec-cmd.c:266 trace: resolved executable dir: C:/Program Files/Git/ucrt64/bin
23:36:52.673482 git.c:506 trace: built-in: git version
23:36:52.705575 exec-cmd.c:266 trace: resolved executable dir: C:/Program Files/Git/ucrt64/bin
23:36:52.707586 git.c:506 trace: built-in: git config list --show-scope -z
3.0.2+0d95999b8fb39bd1045770fe1d69f6a2b07101d7
Soooo… do or don't, be damned either way?