Changelog

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.

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.

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.

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.

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.

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.

1. 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.

Dynamic Pipelines for Bitbucket Cloud are now generally available.

Custom merge checks are now generally available in Bitbucket Cloud. For full details on all the changes coming as part of this release, refer to our deep-dive blog post.

This release includes the following changes:

• Repository Admins:

  • Custom merge checks can now be configured as either “recommended” or “required”.

  • “Recommended” checks will provide feedback to the PR author if failing, but will not block the merge.

  • “Required” checks will block the PR if failing.

  • As per existing classic merge checks, setting custom merge checks as “Required” is only available in premium workspaces.

• Pull request reviewers/authors:

  • Classic merge check and custom merge check results have been consolidated into a single UI Element on the Pull Request screen.

  • The UI behaviour of classic merge checks has been updated to be consistent with the design of custom merge checks.

  • Failing “recommended” merge checks will be visible on the check result sidebar card with a unique visual indicator.

  • Custom merge checks that run “on-merge” have been more clearly distinguished from conventional “pre-merge” checks on the checks result sidebar card.

Introducing new REST API endpoints to facilitate the management of pull request tasks. For further details, please refer to the documentation:

• List tasks on a pull request

• Create a task on a pull request

• Get a task on a pull request

• Update a task on a pull request

• Delete a task on a pull request

The progressive rollout of data security policy events has been completed. 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. You can now subscribe to these events.

Being a new capability however, we are scaling up our processing of these data security policy events over the next few months. In the meantime we have set a upper limit of 50,000 objects. This means that if a customer activates or updates a data security policy that affects more than 50,000 objects, you will receive the first 50k objects in the events and the rest would be omitted.

We intend to raise these limits and will advise once we have reached our final threshold— and have determined our final hard limits.