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.
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.
We're changing how Forge app installations are managed for Bitbucket workspaces. To align with our platform strategy and meet enterprise and regulatory requirements, Bitbucket workspaces must be linked to an Atlassian organization to continue using Forge apps. This change will help us support new features like cross-product apps and data residency.
This change will take effect sometime after March 16, 2026. More details will be available closer to that date.
After the deprecation period, Forge will no longer support apps for Bitbucket workspaces that aren't linked to an Atlassian organization.
Workspaces that aren't linked will have their existing Forge app installations deleted and won't be able to install new Forge apps.
Onboarding happens automatically once a workspace is linked to their company’s Atlassian organization.
To avoid disruption:
Customers need to link their Bitbucket workspace to an organization as soon as possible.
If there are any issues linking workspaces, contact Bitbucket support.
If customers can't link their workspace, but want to keep app data after the deprecation period, contact Ecosystem support.
For step-by-step instructions and more details about this change, check out our community post: Connect your Bitbucket workspace to an Atlassian organization.
Forge platform will be undergoing maintenance:
in FedRAMP production on September 21, 2025 between 5-6am UTC
in commercial production on September 28, 2025 between 5-6am 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.
The allow-popups attribute of the sandbox directive (content security policy) is now supported in Forge Custom UI and UI Kit apps when using * as your client egress configuration. This enables external content (such as those from 3rd party integrations) to open properly in new tabs instead of being blocked by browser security restrictions.
With this enhancement, external content will open in a new browser tab while keeping your Forge app running.
For more information, see the valid domain formats documentation.
In an effort to continue improving performance and scalability of Bitbucket Cloud, we will be deprecating cross-workspace APIs.
On Feb 27, 2026 we will be removing the following endpoints:
/2.0/repositories
/2.0/user/permissions/repositories
/2.0/snippets
/2.0/user/permissions/workspaces
/2.0/workspaces
Bitbucket will be introducing replacements for each of these endpoints with single workspace-scoped versions. We will create another announcement as soon as they become available.
If you are using any of the endpoints listed above in your custom integration or as an extension app that you have built on top of Bitbucket, your integration/app will be impacted and you will need to switch to the new APIs prior to deprecation date.
We’re adding the capability to uninstall and upgrade Forge apps directly within your Bitbucket workspace settings. This means you no longer need to do these tasks in the Distribution screen of the developer console.
Note, the upgrade functionality is only available if the app has a more recent version available.
Rate this page: