Subject: DW's Git integration failing to authenticate with Bitbucket API token (CHANGE-3222 error) — same failure occurs from command line too

Hi all,

I'm running into a persistent Git authentication failure with Bitbucket, and I'm hoping someone has run into this specific combination before.

Setup:

• Dreamweaver (v 21.6) with Git integration enabled for a site
• Remote repo hosted on Bitbucket Cloud
• Windows 11, using Git for Windows / MINGW64 terminal alongside DW's built-in Git panel

What happened:
Bitbucket recently began deprecating app passwords in favor of API tokens (per their CHANGE-3222 notice). I generated a new Atlassian API token with read:repository:bitbucket and write:repository:bitbucket scopes, specifically for this repo.

I updated the corresponding credential in Windows Credential Manager (git:https://[username]@bitbucket.org), replacing the old password with the new token. I also tried:

• Restarting Dreamweaver fully
• Deleting and recreating the credential
• Verifying the remote URL via git remote -v (clean, no embedded token, just https://[username]@bitbucket.org/...)
• Confirming the token was created under the correct Atlassian account (I have two separate Bitbucket logins, and double-checked I was in the right one)

Notably, I have a separate Bitbucket account (a different login altogether, used for a different repo), and I successfully went through this exact same process — generating a new API token and updating Windows Credential Manager — for that account just yesterday, without any issues. Git push/pull has been working fine there ever since. So the general process clearly works; something specific to this second account/repo combination is failing.

The problem:
Both Dreamweaver's Git panel AND a plain git push from the command line (same machine, same repo) fail with the identical error:

remote: CHANGE-3222 - Functionality has been deprecated
remote: App passwords are deprecated and must be replaced with API tokens.
remote: https://developer.atlassian.com/cloud/bitbucket/changelog#CHANGE-3222
fatal: unable to access 'https://bitbucket.org/[username]/[repo].git/': The requested URL returned error: 410

Since both DW and the terminal fail identically, it doesn't seem to be a DW-specific credential cache issue — more likely something about how the token itself is being submitted, or an OAuth/refresh_token entry in Credential Manager potentially interfering (I noticed a separate git:https://bitbucket.org/refresh_token entry alongside the username-specific one).

Has anyone successfully transitioned from Bitbucket app passwords to the new API tokens for Git operations on Windows? Is there a specific format the username/password needs to take (e.g., email vs. username, or a different token type like "repository access token" vs. account-level API token)? And could having multiple Bitbucket accounts/refresh tokens cached on the same machine cause cross-contamination between them?

Any pointers appreciated!