How to run the Bitbucket GCM OAuth force-upgrade checklist

Use this when developer machines or CI images authenticate to Bitbucket Cloud with Git Credential Manager over OAuth and may still be on GCM < 3.0.0 before 2026-11-30. The home tool is local-only. Re-check the Bitbucket changelog and GCM install docs before closing tickets.

1. Step 1. Confirm the Nov 30 2026 OAuth block for GCM < 3.0.0 on the Bitbucket Cloud changelog. Note that PAT and non-GCM setups are unaffected.
2. Step 2. Probe local and CI GCM versions with git-credential-manager --version (or the wrapper your OS ships). Record owner and image tags.
3. Step 3. Open the home checklist: answer version band, machine/bundle class (including Git for Windows), and OAuth vs PAT.
4. Step 4. If auth is PAT or non-GCM, document N/A for the OAuth block and stop—do not force unnecessary upgrades.
5. Step 5. If auth is OAuth and version is old/unknown, upgrade to ≥3.0.0 (prefer 3.0.1) using OS-specific install instructions.
6. Step 6. On Git for Windows, install GCM directly until a bundled release includes a qualified version—do not wait blindly on GfW alone.
7. Step 7. Clear stale credential caches, re-authenticate Bitbucket OAuth once, and re-test fetch/push.
8. Step 8. Scan CI images, runners, and devcontainers; bump GCM or switch those jobs to PAT; attach the exported Markdown plus changelog/release URLs.

Related: FAQ · Use cases · Home tool. Always prefer official vendor documentation for authoritative dates.