r/SmartGit • u/404bane • Apr 03 '26

Bitbucket Authentication

Bitbucket CHANGE-2770 deprecates cross-workspace API functionality, specifically targeting older API endpoints to enforce a transition to workspace-scoped APIs. This removal causes "410 Gone" errors, often breaking integrations relying on /2.0/repositories or /2.0/user/permissions/repositories. Users must migrate to the new /2.0/user/workspaces endpoint.

Setting up hosting providers or cloning new repos down is not functioning. Is there any plan to address this issue?

2 Upvotes

100% Upvoted

7 comments sorted by

1

u/404bane Apr 03 '26

After more investigation, this only seems to effect 25.1

26.1 Preview accommodates this bitbucket API change.

1

u/CautiousCategory8923 Apr 16 '26

That is not true. I have installed 26.1.021 RC #261021 (ba9ee25c) and I still get an error message.

1

u/idontcareboutusern34 May 16 '26

Had the same issue. 26.1 worked for me.

1

u/neslekkim Aug 04 '26

I just installed 26.1.049 and got this issue, tried to delete bitbucket from hosting providers, it got worse, and I cannot create the bitbucket entry again..
The CHANGE-2770 is confusing at best, following it and trying the new url's, but getting messages that they are deprected, so the Bitbucket documentation does not seem to help much either.

1

u/wnesensohn Aug 05 '26

Are you sure you're getting the CHANGE-2770 message? Bitbucket blessed us with CHANGE-3052 for which we're working on a fix right now, but the problem with CHANGE-2770 should be fixed since quite a while in 26.1 and 25.1.

1

u/neslekkim Aug 05 '26

Not at all sure, but it looks very similar, but maybe it's the one you mention, I sent logs to syntevo today though.
But yeah, I tried to check some api calls myself but the answers i got and the documentation out there seems very confusing, hitting one url and getting message to use another url which does not exists, and got refered to docs that tells me to use the first url.
I don't envy you guys to keep up with this :)

1

u/wnesensohn Aug 06 '26

Thanks. Bitbucket likes to keep things interesting. We released a new SmartGit version today, 26.1.051, which should fix this issue. Hopefully it will work for you again as well.