⚠ Bitbucket GCM OAuth
Nov 30 2026

Check GCM version, Windows bundle lag, and OAuth vs PAT before Nov 30

Local force-upgrade checklist. Not Bitbucket Cloud SaaS. Not affiliated. Verify on Atlassian changelog + GCM releases.

A · GCM version

B · Machine / Windows fork

C · Auth path

How it works

  1. Answer GCM version band, machine/bundle class, and OAuth vs PAT.
  2. Get a Nov 30 force-upgrade checklist with a Windows direct-install fork when Git for Windows lags.
  3. Copy Markdown into your IT/CI ticket — we never install software or call Bitbucket.

On 2026-11-30, Bitbucket Cloud blocks Git requests that use OAuth via GCM versions prior to 3.0.0 because rotating refresh tokens are required. PAT users and non-GCM setups are unaffected. Git for Windows may still bundle an older GCM—install a qualified GCM directly until a bundled release catches up.

vs New Relic Synthetics Node22 force-upgrade / Workspace MCP OAuth: this is local Git Credential Manager version × auth-path, not a cloud monitor runtime and not Google Workspace MCP agentic OAuth.

Next: how-to · FAQ · use cases. Verify on the Bitbucket changelog and GCM v3.0.1 release notes.