View end of support announcements for Bitbucket Cloud
We occasionally remove existing features and functions from Bitbucket Cloud in order to provide the best user experience possible. We don't make these changes lightly and know this might directly affect the workflows and functionality you use every day. We carefully consider usage, alignment with product direction, and operating overhead when deciding to end support for a feature.
We will make our best effort to provide advance notice to everyone using a feature before we end support for that feature. When possible we'll also offer alternatives or point to a new feature which replaces the function of the feature we are removing.
In addition to updates on this page, notifications may include email, in-app messaging, API responses, and/or blog posts on blog.bitbucket.org.
Features and functions ending support
The following table summarizes the end of support announcements for future Bitbucket Cloud releases.
Feature
End of support
Who it affects
Details
Atlassian account passwords for API and Git activity will be disabled 1 March 2022
March 01, 2022
Users signed up after 2021-09-13T00:00:00.000Z and trying to use non-interactive auth via bitbucket’s git / api operation using basic username/password based auth.
As previously announced in the Bitbucket blog, beginning 1 March 2022, Bitbucket users will not be able to use their Atlassian account passwords for API and Git activity.
Additionally, we've recently announced that new users with Atlassian accounts created on or after 13 September 2021 will not be able to use their account passwords for these Bitbucket activities.
For API and Git operations, an app password with the necessary scopes can be used in place of your account password. Please see Bitbucket Cloud documentation for a detailed explanation of what app passwords are and how to create and use them.
Smart mirroring is being deprecated
April 21, 2021
Users or teams currently using smart mirroring
Starting on April 21, 2021, smart mirroring in Bitbucket Cloud will no longer be available for new installations. Existing installations will continue to function as usual, but we will no longer be supporting this feature.
This table summarizes the end of support announcements for past Bitbucket Cloud releases.
On 01 Jun 2020, Bitbucket removed the AWS CodeDeploy app in favor of its AWS CodeDeploy pipe. That means the AWS CodeDeploy app will no longer be listed in the marketplace, and new installations will be disabled. On 01 Jun 2020 any existing installations of the AWS CodeDeploy app will be removed. Read more about this change.
Anyone using OAuth 1.0 for authentication with Bitbucket
We recommend using OAuth 2 as an authentication method going forward.
General invites
May 1, 2017
Anyone using the invitations endpoint without specifying a team or repository
Use team or repository invites to easily add new teammates to Bitbucket and give them the access they need.
Following individual accounts and teams
April 15, 2017
Users following other user or team accounts
Repository, pull request, and issue following will continue to work the same way. We recommend following the repositories you care about to stay on top of relevant activity. The full list of the accounts you follow and are followed by is still available via the API.
Team-level passwords
March 31, 2017
Teams using passwords to sign in to the Bitbucket web UI
We initially made this change in 2014 but allowed some teams to temporarily login using a team password.
