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.
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.
Effective 18 Aug 2025, the following fields in the Bitbucket Cloud REST API will be updated to support larger values:
Pull request comment ID: Will change from int32 to int64
Pull request task ID: Will change from int32 to int64
This change may affect API clients and webhook consumers that explicitly handle these fields as 32-bit integers. Please update your integrations to handle 64-bit integer values for these fields.
The following UI Kit components are now generally available:
https://developer.atlassian.com/platform/forge/ui-kit/components/adf-renderer/
https://developer.atlassian.com/platform/forge/ui-kit/components/calendar/
https://developer.atlassian.com/platform/forge/ui-kit/components/checkbox-group/
https://developer.atlassian.com/platform/forge/ui-kit/components/empty-state/
https://developer.atlassian.com/platform/forge/ui-kit/components/inline-edit/
https://developer.atlassian.com/platform/forge/ui-kit/components/list/
https://developer.atlassian.com/platform/forge/ui-kit/components/popup/
https://developer.atlassian.com/platform/forge/ui-kit/components/time-picker/
No code changes are required. These components will now follow the 6 month deprecation period if any breaking changes were to be made.
A new RFC is available for review at https://community.developer.atlassian.com/t/rfc-99-upcoming-changes-to-bitbucket-navigation/93702.
As part of the Atlassian visual refresh updates, we updated the UI Kit Icon component. Some glyphs get a new look, and many more glyphs have been added. There are also a number of deprecations, as detailed below.
The size prop will only support the values "small" and "medium". The value "large" is now deprecated and will be removed.
The prop primaryColor has been renamed to color.
The prop secondaryColor is now deprecated and will be removed.
Some glyphs haven been replaced and others will be removed. Visit the Icon migration guide for information on finding a replacement.
The new default size for icons will change from 24x24 pixels to 16x16 pixels.
All deprecations and breaking changes will take place on Jan 1, 2026. Until then, the new Icon component will be fully backwards-compatible. Any deprecation will trigger a console warning prefixed with [@forge/react: Icon] on non-production environments.
We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.
Developers can start using app events by implementing the https://developer.atlassian.com/platform/forge/manifest-reference/modules/event/ module in their apps. For detailed guidance and examples, refer to https://developer.atlassian.com/platform/forge/events-reference/app-events/.
To publish events using the runtime API, you need at least version 2.0.0 of the @forge/events dependency. Add this to your package.json:
1
2
3
4
5
{
"dependencies": {
"@forge/events": "^2.0.0"
}
}Blob objects can now be sent and received via the events API. This enhancement allows for more efficient data handling and transmission within the API.
Update to the latest version of @forge/bridge with npm install --save @forge/bridge@latest
With the Forge CLI 11.5.0 release, we've enhanced the Forge platform to let you specify the memory available to functions at runtime by setting the memoryMB property in the Manifest (https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2) . Increasing the function memory also increases its CPU allocation. The memory value can now be set between 128 MB and 1,024 MB, doubling the previous limit of 512 MB. If you do not configure the function memory, the default memory allocation of 512MB applies to your function. This change helps address out-of-memory (OOM) issues by allowing higher memory allocation.
For more information on configuring Forge function memory, see https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2.
For details on the relationship between memory and CPU allocation, refer to the https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html.
Rate this page: