timetobail
My stack

Bitbucket · Forced move · Announced October 13, 2026 · Sources checked Oct 17

Time to bail on Old Git Credential Manager OAuth on Bitbucket Cloud?

Time to Bail · Boarding pass

FromOld Git Credential Manager OAuth on Bitbucket Cloud
ToYour pick

Act. You can stay.

From November 30, 2026, Bitbucket blocks these Git requests. Upgrade GCM to 3.0.0 or later.[1]

Act means: change a setting or plan before the date. You can stay.

Gate closes
Blocked from
Time left
43days
Status
Act

Bitbucket blocks old Git Credential Manager OAuth on November 30, 2026

From November 30, 2026, Bitbucket Cloud blocks some Git requests. These sign in with OAuth 2.0 through Git Credential Manager (GCM) older than 3.0.0. Old GCM versions cannot handle rotating OAuth refresh tokens. Git without GCM, and GCM with personal access tokens, are not affected.

Email me 7 days before Nov 30

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

How it is winding down

  1. Oct 13AnnouncedDone
  2. Nov 30Blocked fromNext

What to do before November 30

Tick steps as you go. Your progress stays in this browser.

  1. Check your GCM version

    Run git credential-manager --version on each machine that pushes to Bitbucket.

  2. Upgrade GCM

    Install GCM 3.0.0 or later. On Windows, install GCM on its own for now.

  3. Push once to test

    The warning after git push should be gone.

Email me 7 days before Nov 30

One email with the first steps. Nothing else.

We email you one link to confirm (double opt-in). Nothing starts until you click it. Unsubscribe any time. How we use your email.

Or add the date to your calendar: Apple or Outlook (.ics) · Google Calendar

Facts we checked

Facts and their sources
Blocked fromNovember 30, 2026[1]
AffectedGit Credential Manager older than 3.0.0, set up with OAuth 2.0[1]
Not affectedGit without GCM, and GCM with personal access tokens[1]
ReasonOld GCM versions do not support rotating OAuth refresh tokens, which Bitbucket now enforces[1]
Warning nowAffected users see a message after each git push[1]
FixUpgrade GCM to version 3.0.0 or higher[1]
Git for WindowsIt bundles GCM; until a new release has the needed GCM, install GCM on its own[1]
AnnouncedOctober 13, 2026[1]
GCM users on OAuth 2.0 before 3.0.0Git requests blocked from November 30, 2026[1]

Sources

Check it yourself. Every fact above links here.

  1. Bitbucket Cloud changelog: Git Credential Manager (GCM) upgrade required for continued OAuth 2.0 Git authentication Atlassian · primary · checked Oct 17
Read the published editorial report

What changed

Time to bail on Old Git Credential Manager OAuth on Bitbucket Cloud? Act. You can stay. From November 30, 2026, Bitbucket blocks these Git requests. Upgrade GCM to 3.0.0 or later.

On our scale this is Act: change a setting or plan before the date. You can stay.

From November 30, 2026, Bitbucket Cloud blocks some Git requests. These sign in with OAuth 2.0 through Git Credential Manager (GCM) older than 3.0.0. Old GCM versions cannot handle rotating OAuth refresh tokens. Git without GCM, and GCM with personal access tokens, are not affected.

Here are the facts we checked:

  • Blocked from: November 30, 2026 (Atlassian)
  • Affected: Git Credential Manager older than 3.0.0, set up with OAuth 2.0 (Atlassian)
  • Not affected: Git without GCM, and GCM with personal access tokens (Atlassian)
  • Reason: Old GCM versions do not support rotating OAuth refresh tokens, which Bitbucket now enforces (Atlassian)
  • Warning now: Affected users see a message after each git push (Atlassian)
  • Fix: Upgrade GCM to version 3.0.0 or higher (Atlassian)
  • Git for Windows: It bundles GCM; until a new release has the needed GCM, install GCM on its own (Atlassian)
  • Announced: October 13, 2026 (Atlassian)
  • GCM users on OAuth 2.0 before 3.0.0: Git requests blocked from November 30, 2026 (Atlassian)

You can stay on Bitbucket. You have to change a setting or plan before the date.

Leaving is a choice here, not a must.

Atlassian is the main source for this page. Bitbucket has not said more than what is listed here. If a fact is not on this page, we do not know it yet.

Who is affected

GCM users on OAuth 2.0 before 3.0.0: Git requests blocked from November 30, 2026.

The date to remember is November 30, 2026. Make the change before then.

What to do before November 30

  1. Check your GCM version. Run git credential-manager --version on each machine that pushes to Bitbucket.
  2. Upgrade GCM. Install GCM 3.0.0 or later. On Windows, install GCM on its own for now.
  3. Push once to test. The warning after git push should be gone.

A few tips:

  • Make the change yourself before the date. Do not wait for the last reminder email.
  • Write down your current plan or settings first, so you can compare after the change.
  • After the change, open your settings again and check that it worked.

How to tell your users

If the change affects your members or team, send one short email. Say what changes for them and when. Put the most important line first.

If there is a date, send a short reminder a few days before it. Keep a copy of the list you sent it to.

Options people mention

Listed for convenience. Not ranked. Not paid. These names come up in threads and reviews; that does not show where people moved.

Before you pay, check the price page of each tool yourself. Prices change, and we only list what our sources say.

Questions people ask

No questions collected yet.

Sources

Thanks.

Did this answer your question?

Run SaaS spend at work? Get these changes before the invoice

Arrivals · for builders

Building where they land?

People on Old Git Credential Manager OAuth on Bitbucket Cloud can stay if they make the change. Some would rather leave. Get the playbook for this change, and list your product here.

Listing is free. An editor checks it. Not ranked. Not paid.

Open the playbookList your product