FAQ

What happens to GCM OAuth <3.0.0 after 2026-11-30?

Bitbucket Cloud will block Git requests that authenticate with OAuth via GCM versions prior to 3.0.0 because rotating refresh tokens are required. Impacted users may already see post-push warning messages before the cut date.

Do PAT users or non-GCM setups need to upgrade?

No action is required for the Nov 30 OAuth block if you are not using GCM, or if GCM is configured with personal access tokens instead of OAuth. Still keep general Git tooling patched for other reasons.

Why does Git for Windows need a direct GCM install right now?

Git for Windows bundles GCM but releases are tied to upstream Git timing. At announcement time there was no GfW release bundling a qualified GCM, so Windows users should install a suitable GCM directly and watch for a later bundled version.

How do I verify GCM version on a CI image?

Run the version command inside the image or job, or inspect the installed package layer. Export image tag + version into the inventory board section of your ticket so runners are not forgotten.

Should I clear cached credentials after upgrading?

Yes if pushes still fail after a binary upgrade. Stale refresh tokens or mixed caches are a common footgun; re-auth once after clearing.

Does this site install GCM or call Bitbucket for me?

No. It only builds a local Markdown checklist. You install GCM via official docs and test Git yourself.

Is this official Atlassian documentation?

No. Unofficial local helper. Not affiliated with Atlassian or the GCM project.

Do you store my answers?

No. Browser session only; clipboard copy stays on your machine.