Bitbucket Cloud blocks Git Credential Manager's OAuth before 3.0.0 on November 30, 2026
If Git signs in to Bitbucket Cloud through Git Credential Manager's browser login (OAuth), pull and push stop working on November 30, 2026 unless Git Credential Manager is 3.0.0 or newer. IntelliJ IDEA, PyCharm, WebStorm and Rider run the Git installed on your computer, so this applies to them too. On Windows that is usually the Git Credential Manager that came with Git for Windows, and Git for Windows does not include version 3 yet.
Who is affected
From Bitbucket Cloud's changelog (October 13, 2026): older versions do not support the rotating OAuth refresh tokens that Bitbucket now enforces.
| You use | What to do |
|---|---|
| Git without Git Credential Manager (or SSH) | Nothing |
| Git Credential Manager with a token (API token, access token) | Nothing |
| Git Credential Manager with OAuth (signed in through the browser) | Git Credential Manager 3.0.0 or newer by November 30, 2026 |
Until then, affected users see a message after each git push, the changelog says.
Check your version
git credential-manager --version git config --show-origin --get-all credential.helper
The first prints the version (for example 2.7.3+…). The second shows whether Git uses it: manager from C:/Program Files/Git/etc/gitconfig is Git for Windows' default.
Why updating Git for Windows is not enough yet
Git Credential Manager 3.0.1 came out on October 6, 2026 (release; its notes list "Support for Bitbucket Cloud's updated OAuth tokens"). The newest Git for Windows is 2.56.0(3) of October 22, 2026, and its release notes last name Git Credential Manager v2.9.0 (bundled since July 2026). The changelog says the same: install Git Credential Manager directly until Git for Windows includes it.
Way out 1: install Git Credential Manager 3
- Windows: from the release page,
gcmuser-win-x64-3.0.1.exeinstalls for your user without administrator rights;gcm-win-x64-3.0.1.exeinstalls for all users and needs them (arm64 builds too). Its install guide says a standalone install overrides the one bundled with Git for Windows. - macOS (Homebrew):
brew upgrade --cask git-credential-manager
Then run git credential-manager --version again. If you also use Azure Repos, version 3 changes how Git signs in there too (what changed).
Way out 2: use an API token instead of OAuth
Token sign-in is not affected. Create an Atlassian API token and use it for Git as described in switching Git to an API token. To make Git Credential Manager ask for the token instead of opening the browser, limit its Bitbucket sign-in to tokens (configuration):
git config --global credential.bitbucketAuthModes basic
Bitbucket pull requests in IntelliJ IDEA
Pull Request Inbox for Bitbucket, a plugin by Lesstep for JetBrains IDEs 2024.1 or later, talks to Bitbucket's API with its own Atlassian API token (or an access token), kept in the IDE's password safe; it does not go through Git Credential Manager. Git itself (pull, push, checkout) still uses your Git and its credential helper. The review inbox, diffs and discussions are free; approving, commenting and merging are Pro, with a 30-day trial.
Get it on JetBrains Marketplace
Bitbucket and Atlassian are trademarks of Atlassian; IntelliJ IDEA is a trademark of JetBrains s.r.o. This page is not affiliated with or endorsed by Atlassian, JetBrains or the Git Credential Manager project.
More: Bitbucket pull requests in PyCharm · "error: 410" after app passwords · Bitbucket Cloud SSH moves to ssh.bitbucket.org · 日本語