This changelog is the source of truth for all changes to the Bitbucket API and Bitbucket Connect API that affect people using Bitbucket Cloud and developing Bitbucket Cloud apps.
To ask any questions related to Bitbucket Cloud development please visit the Bitbucket Cloud developer community.
As previously mentioned in CHANGE-2770, support for several cross-workspace APIs has ended.
We are announcing the availability of two new public REST APIs that return information about the accessible workspaces for a user:
These new endpoints can be used alongside existing single-workspace scoped APIs to serve as replacements for the deprecated APIs.
Below is a table summarizing the deprecated APIs and the corresponding alternative APIs that we suggest transitioning to.
| Deprecated API description | Deprecated endpoint and link | Suggested alternative APIs |
1 | Returns a paginated list of all public repositories. |
|
|
2 | Returns an object for each repository the caller has explicit access to and their effective permission. |
|
|
3 | Returns all snippets. |
|
|
4 | Returns an object for each workspace the caller is a member of, and their effective role. |
|
|
5 | Returns a list of workspaces accessible by the authenticated user. |
|
For the first three deprecated APIs, if you already have a single workspace, simply transition to the workspace-scoped alternative by including the workspace slug or UUID in the request path.
However, if you do not already have a single workspace, we suggest using the workspace‑scoped APIs in combination with the new /2.0/user/workspaces API.
Use the /2.0/user/workspaces to get all accessible workspaces for the user
Request to workspace‑scoped alternative endpoint (example: /2.0/repositories/{workspace})
Option 1: select one accessible workspace to use in a request to the scoped endpoint (1 request)
Option 2: make a request for each accessible workspace and aggregate the results (N requests)
The following UI Kit components are now generally available:
Comment, which displays discussions and user feedback.
Pressable, which is a primitive for building custom buttons.
CommentEditor, provides a contained comment editor UI with a simple toolbar.
ChromelessEditor, provides a simple text editor that does not have a toolbar.
For more information, see the component documentation.
To access these components, you will need to update your app to the latest version of @forge/react. In the terminal of your project directory, run:
npm install --save @forge/react@latest
We’ve added the module bitbucket:workspacePersonalSettingsPage to Forge. You can use this module to build a custom workspace settings page. For more information, see Bitbucket workspace personal settings page.
We’re retiring support for OAuth 1.0 and Implicit Grant flows for Bitbucket Cloud on Feb 27, 2026. These methods are being removed due to known security risks and alignment with modern OAuth 2.0 standards.
If you’re still using OAuth 1.0 please plan to migrate to Oauth 2.0 before Feb 27, 2026 using our authentication guide which has full details on how to set this up.
After the cutoff, requests using OAuth 1.0 or implicit grants will no longer be accepted.
For help migrating, see our updated authentication guide or contact support.
Following the Preview release, the Forge Automation Actions is now generally available. The Automation action module allows you to extend the Automation Platform and add new Forge-based actions to your app. With this release Forge Actions can now output smart values, enabling seamless data flow and dynamic automation.
For more information, see the Forge Automation Action module documentation.
bitbucket:projectSettingsMenuPage module is now available. You can use this module to build a custom project settings page. See the project settings menu page for details.
bitbucket:repoCodeFileViewer module is now available. You can use this module to build a custom file viewer. See the file viewer page for details.
We've introduced the bitbucket:workspaceGlobalPage module for Forge apps. Your app will now appear as a menu item in the Apps section of the Bitbucket workspace navigation, displaying your custom page content when users select it.
To use this module, update your app’s manifest to include bitbucket:workspaceGlobalPage.
For implementation details and examples, see the bitbucket:workspaceGlobalPage module reference.
Forge platform will be undergoing maintenance in commercial production on November 23, 2025 for approximately 1 minute between 5:30-6:30am UTC
During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
Starting February 27, 2026, the Bitbucket Cloud REST API endpoint to fork a repository will not allow forking outside the parent workspace. Currently, if the workspace parameter is not added, the fork will be created in the requesting user's workspace. On 2/27/26, if the workspace slug is not added, it will default to the parent workspace. If another workspace is specified, an error will be returned. Applications using this endpoint should be updated to create forks within the parent workspace only.
As part of previously announced changes to improve diff performance, Bitbucket Cloud’s compare two commits and compare two diff stats REST endpoints will begin returning a topic diff (three-dot diff) by default, instead of the current default, preview-merge diff.
This change will be effective November 17, 2025.
Consumers can specify the merge=true parameter to explicitly request a preview-merge diff. This parameter is already supported but will be removed in the future. We will post a separate changelog entry when we have further details about the timeline for its removal.
When defining resolvers, the front-end code can share the types with the backend so the invocation interface is type-safe. This helps catch potential errors during compilation.
We've enhanced the Forge Bitbucket event for pull request reviewer status updated. The event payload now includes a new reviewers field, which provides the latest status of each reviewer on the pull request.
This addition makes it easier to track reviewer decisions and automate workflows based on reviewer status.
For more information and example payloads, see the Bitbucket Forge events.
Forge Automation Actions is now available in Preview. This feature allows you to extend the Automation Platform and add new Forge-based actions to your app. During Preview, the Automation Actions in your app can be used in production environments.
For more information, see the Forge Automation Action documentation and share your feedback to help us improve
Forge platform will be undergoing maintenance in commercial production on October 12, 2025 for approximately 1 minute between 3-4am UTC
During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
Rate this page: