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.
As a workspace admin, you can now access the direct distribution link for a Bitbucket Forge app installed on your workspace.
To do this, go to Workspace settings > Installed apps and then select the Manage link next to the app.
The UserPicker component is now supported for Bitbucket Forge apps. Users available for selection are scoped to the current workspace users.
Bitbucket API scaled rate limits are now generally available to customer workspaces with more than 100 paid users.
This release includes the following changes:
For applicable API endpoints, 10 extra API requests per hour are granted for every additional paid user in workspaces with more than 100 paid users
The maximum rate limit is set at 10,000 requests per hour
Scaled rate limits only applies to authenticated requests using Access Tokens and Forge applications using the app user(asApp) to make requests to Bitbucket REST APIs
For endpoints with scaled rate limits, API consumers receive additional response headers: X-RateLimit-Limit
, X-RateLimit-Resource
, and X-RateLimit-NearLimit
For more information on scaled rate limits, visit the following documentation.
We’re launching the new Forge Roadmap, updated every hour with the latest insights from our internal Jira Product Discovery. Developers and partners can use this roadmap to stay informed about upcoming features and changes. If you have feedback, share it in our community thread.
EDIT, 30-Sep-2024: This RFC is now closed.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-62-dark-mode-theming-are-coming-to-bitbucket-cloud/83062.
The List workspace pull requests for a user operation returns all pull requests authored by the specified user in a given workspace. This new operation works the same way as the deprecated List pull requests for a user but requires the {workspace}
path parameter.
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.
As previously announced, the List pull requests for a user operation will be removed on Feb 7, 2025.
We're announcing new IP ranges that will soon be available for requests from external clients, such as browsers and API integrations:
13.35.248.0/24
13.227.180.0/24
13.227.213.0/24
These ranges won't be used to make outgoing connections from Atlassian Cloud to remote systems, for example, webhooks.
To prepare for this change, update your firewalls and other security measures to allow connections to the new IP ranges.
For more information, see IP addresses and domains for Atlassian Cloud products, which includes instructions on how to receive notifications of changes, as well as links to machine-readable lists of our IP ranges.
The bitbucket:mergeCheck
module invocation payload now includes additional information related to pull request merge. The payload now provides:
The merge commit message (truncated at 1000 characters if necessary)
An indicator of whether the commit message was truncated
The merge strategy used
An indicator of whether to close the source branch after the merge
See the module documentation for more details.
EDIT, Aug 23, 2024: The workspace-scoped replacement API is now available.
On Feb 7, 2025 Bitbucket will be removing the List pull requests for a user endpoint, which fetches pull requests authored by a given user across all of their workspaces.
Prior to that date, Bitbucket will introduce a workspace-scoped version of the endpoint. We will post a separate announcement when the new endpoint is available.
Instead of the deprecated API /2.0/pullrequests/{selected_user}
we will soon introduce a new API that will be workspace-scoped.
If you only have a single workspace, migrating to a new API will be fairly simple - you will just need to include the workspace name in the URL.
Otherwise, if you are looking for pull requests authored by a given user across multiple workspaces, you will need to:
Get the list of available workspaces using List workspaces for user endpoint
Iterate over the list of workspaces and use the new API to get pull requests authored by a given user in each workspace
In the latest version of @forge/react
(version 10.5.0), we are releasing a new set of UI Kit components alongside a few changes to existing components.
We are releasing the following new UI Kit components into Preview:
List
CheckboxGroup
Calendar
TimePicker
InlineEdit
Popup
EmptyState
For existing components, the following changes are being made:
Tag component now includes href
prop
Icon component now includes primaryColor
and secondaryColor
props
For more information on the capability of these components, please find the corresponding component documentation
To update your UI Kit app to the latest version, in the terminal of your project directory, run the following command:
npm install --save @forge/react@latest
We’ve added a new avi:bitbucket:updated:pullrequest-reviewer-status
product event for Bitbucket Forge. You can use this event to invoke your Forge app whenever a reviewer’s status on a pull request changes.
For more information, see Pull request reviewer status updated.
We’ve extended the functionality of List users in a workspace API to support filtering the response by user’s email address. You can retrieve account IDs from the list of email addresses.
For more information, see the documentation.
The upper limit of for Data security policy events has been increased to 200,000 objects, from the previous limit of 50,000 objects.
How does the upper limit work
This means that if a customer activates or updates a data security policy that affects more than 200,000 objects, you will receive the first 200k objects in the events and the rest would be omitted.
Data security policies help customers keep their organization’s data secure by letting them govern how users, apps, and people outside of their organization can interact with content such as Confluence pages and Jira issues.
Data security policy events are generated when installed apps' access to certain data within Confluence, Jira, Jira Service Management, or Jira Software has been blocked by an administrative policy with an App access rule. App developers can subscribe to these events, we encourage you to read the Developer guide.
Forge functions can now interact with remote backends utilising Forge Remote. This capability makes it simpler and more secure to integrate remote backends with your Forge app.
See Forge Remote - Calling a remote backend from a Forge function for more information.
requestBitbucket is now available in @forge/bridge
, so you can make Bitbucket API fetch requests from the front end of a UI Kit or custom UI app. For more information on using requestBitbucket
, see the Part 2: Call a Bitbucket API tutorial.
Rate this page: