Changelog

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:

1. /2.0/repositories

2. /2.0/user/permissions/repositories

3. /2.0/snippets

4. /2.0/user/permissions/workspaces

5. /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.

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.

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.

Internationalization (i18n) for Forge apps is now generally available. This allows you to add translation support to your app so that it can adapt based on a user’s language and locale.

In addition to the Confluence and Jira modules that were supported during the EAP, internationalization support can now also be added to Bitbucket, Compass, and Jira Service Management modules, as well as Forge resolvers.

For more information, see Internationalization.

Forge Remote Data Residency realm migrations is now available in GA. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

We will not be issuing any new waivers for apps that need to request or store Atlassian user API tokens. This decision is part of our ongoing commitment to enhancing security and protecting customer trust.

Forge Apps that have already been granted waivers must ensure a lack of alternative solutions within Forge. They can continue to operate, but no additional waivers will be granted for new modules or new functionality within the same app.

Connect apps that have been granted waivers and any existing Connect app requesting or storing Atlassian user API tokens are required to migrate to Forge, with tokens stored in Forge encrypted storage.

With the introduction of draft pull requests in Bitbucket Cloud, REST API endpoints for pull requests now include a boolean attribute draft that can be used in both read and write operations. Webhook event paylods for pull requests also now include the draft parameter.

Note that the draft attribute is a separate field from the pull request state. Draft pull requests will always have state: "OPEN" and draft: true.

For further info, please see our developer documentation.

• REST API docs

• Webhook event docs

We have updated our UI Kit components, Text and Heading to make them more flexible:

Text

• Now supports align, as, color, maxLines, size and weight properties.

For more information, see Text component documentation.

Heading

• You can now control how the Heading component appears by setting a value for size, while the as prop controls the HTML element's rendering.

For more information, see Heading component documentation.