Changelog

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.

Following the deprecation announcement on 28 Aug 2024, we have now removed UI Kit 1 from the Forge platform.

For apps still using UI Kit 1, customers will see that their app version is outdated due to a deprecated platform component.

You will need to upgrade to the latest version of UI Kit for your app to work. If you are in the process of upgrading your UI Kit 1 app, please refer to these resources to guide you through the transition:

• Example of migrating an app from UI Kit 1 to UI Kit

• Upgrade from UI Kit 1 to the latest version

• Upgrade to @forge/react major version 10

• Notify site admins using the Forge app with UI Kit 1

Forge platform will be undergoing maintenance on March 02, 2025 between 00:30 AM to 03:30 AM. During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

• View existing installations

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.

As announced in a previous deprecation notice, on Feb 20, 2025 Bitbucket removed the List pull requests for a user API endpoint, which fetches pull requests authored by a given user across all of their workspaces. The removed endpoint now returns a 404 error.

Please migrate your usage to the replacement API endpoint, List workspace pull requests for a user.

We’ve added a new Bitbucket Forge product events: avi:bitbucket:created:commit-comment. You can use these events to invoke your Forge app function when a commit comment is created. For more details see https://developer.atlassian.com/platform/forge/events-reference/bitbucket/.

All the Forge Bitbucket UI modules extension data now include a location property, which is available by calling the useProductContext hook. It provides the full URL of the host page where the module is displayed in. For more details, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-bitbucket/.

The following Forge Bitbucket modules now support view.createHistory() via @forge/bridge:

• bitbucket:repoMainMenuPage

• bitbucket:repoSettingsMenuPage

• bitbucket:workspaceSettingsMenuPage

App developers can now utilize a path segment at the end of the page URL to maintain page history within their app. For more details, see https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/view/#createhistory.

We’ve added two new Bitbucket Forge product events: avi:bitbucket:resolved:pullrequest-comment and avi:bitbucket:reopened:pullrequest-comment. You can use these events to invoke your Forge app function when a pull request comment is resolved or reopened. For more details see https://developer.atlassian.com/platform/forge/events-reference/bitbucket/.

We’ve introduced two new Bitbucket Forge product events: avi:bitbucket:created:build-status and avi:bitbucket:updated:build-status. You can use these to invoke your Forge app function when a build status is created or updated. For more details see https://developer.atlassian.com/platform/forge/events-reference/bitbucket/.

As mentioned in a previous deprecation notice, on Feb 20, 2025 Bitbucket will be removing the List pull requests for a user API endpoint, which fetches pull requests authored by a given user across all of their workspaces.

We have introduced a new endpoint, List workspace pull requests for a user, which returns pull requests authored by the specified user in a given workspace. This new operation works the same way as the deprecated endpoint but requires the {workspace} path parameter.

API consumers must migrate their usage to the new endpoint before Feb 20, 2025.

We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com

The read:user:bitbucket Forge app scope has been removed from the following API endpoints since it is considered unnecessary. This is a non-breaking change and Forge app developers have the option of removing the read:user:bitbucket Forge app scope from apps that use the following endpoints.

We've introduced the bitbucket:repoCodeOverviewPanel Forge module. This module adds an expandable panel on the Source page of a repository to display custom information defined in a Forge App.