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.
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.
To retrieve pull requests authored by a given user across multiple workspaces, follow these steps:
Get the list of available workspaces using the List workspaces for user operation.
Iterate over the list of workspaces and use the List workspace pull requests for a user operation to get requests authored by the user in each workspace.
If you’re using GitKraken Desktop with Bitbucket Cloud repos, you should update to version 10.6.3 or later. Previous versions were making use of the deprecated endpoint, and will stop working correctly as of Feb 20, 2025.
We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com
We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.
For details on how this change affects you and for guidance on migration, please refer to the documentation available on Atlassian Developer .
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.
Route | Before | After |
|---|---|---|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
The following API endpoints have been updated to no longer require the read:user:bitbucket Forge app scope:
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.
This enhancement allows developers to customize the information displayed in the repository Source page, improving the visibility of critical data. For more information, see Bitbucket code overview panel.
The environment key is now included in the URLs for the following modules:
Note: You will need to update any bookmarks or saved links to these pages to view your Forge app in the left navigation.
For example, for repoMainMenuPage the URL path is changing per below:
from: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeAppModuleKey}
to: /{workspaceSlug}/{repositorySlug}/forge/{forgeAppId}/{forgeEnvironmentKey}/{forgeAppModuleKey}
The page loaded directly with the old URL will no longer have menu items on the left navigation:
To navigate to the new URL:
Select the breadcrumb link (test_repo1 in the screenshot above) to load the repo page.
Select the menu item for the Forge page on the left navigation.
All your apps will now be listed on the left navigation.
We've introduced the bitbucket:repoPullRequestOverviewPanel Forge module. This module adds an expandable panel on the PR Overview tab to display custom information defined in a Forge App.
This enhancement allows developers to customize the information displayed in pull request overviews, improving the visibility of critical data. For more information, see Bitbucket pull request overview panel.
The AdfRenderer component provides a way to render a valid ADF document, using the same renderer that Atlassian uses internally to render ADF content in Confluence pages, Jira work items, and so on. See ADF renderer for the full docs.
The ADF renderer component also allows you to replace node types that are unsupported in the context of a Forge app with replacement content, or remove them entirely.
See Atlassian Document Format for information on valid nodes.
Run npm i @forge/react@latest to install the preview version of the components and try them out now.
We have now removed the UI Kit @forge/react version 9 from the Forge platform. This UI Kit version was deprecated on Aug 28, 2024.
We recommend using the latest version of UI Kit (@forge/react10).
For more information, see our deprecation policy.
Bitbucket Cloud now allows custom merge checks to be configured at the workspace and project levels and enables rules set at higher levels to be inherited, reducing redundant configurations. The UI has also been redesigned to offer clearer guidance around the initial setup of the feature and make it easier for admins to configure checks across all levels.
For full details, refer to to our blog post.
We now accept bug and incident reports under a single new request type: Ecosystem Support Request. This change simplifies the process of reporting issues to our support team, so that we can handle your issue more efficiently, and ensure consistent handling for all critical issues, particularly incidents.
We’ve also detailed the scope of our Developer and Marketplace support, so you have a better understanding of supported issues and response times.
We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com
We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.
For details on how this change affects you and for guidance on migration, please refer to the documentation available at http://developer.atlassian.com .
Rate this page: