Last updated Dec 12, 2024

Changelog

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.

12 December 2024

Added Introducing UI Kit ADF Renderer component in preview

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.

More details

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.

5 December 2024

Removed  UI Kit @forge/react version 9 has been retired

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.

19 November 2024

Announcement Workspace and project level custom merge checks are now available

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.

Announcement New process for reporting bugs and incidents to Ecosystem support

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.

10 November 2024

Deprecation Notice Third-party package mirrors will no longer be available

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

More details

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 .

7 November 2024

Added Git operations via https now available in Bitbucket Forge apps using Forge remote

You can now execute git operations from Forge remote backend of a Bitbucket Forge app using app system or user tokens. See Forge remote documentation for details.

2 October 2024

Added Workspace admins can now access Bitbucket Forge app links from workspace settings

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.

1 October 2024

Fixed Support UserPicker in Bitbucket Forge

The UserPicker component is now supported for Bitbucket Forge apps. Users available for selection are scoped to the current workspace users.

26 September 2024

Announcement Scaled rate limits are now in General Availability (GA)

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.

24 September 2024

Announcement Improved Forge public roadmap

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.

30 August 2024

Request for Comments (RFC) RFC: Dark Mode & Theming are coming to Bitbucket Cloud

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.

23 August 2024

Added List workspace pull requests for a user

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.

More details

To retrieve pull requests authored by a given user across multiple workspaces, follow these steps:

  1. Get the list of available workspaces using the List workspaces for user operation.

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

21 August 2024

Announcement Additional IP ranges for Atlassian Cloud

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.

More details

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.

19 August 2024

Added Improved Bitbucket merge check module payload

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.

7 August 2024

Deprecation Notice Removing API for getting list of pull requests for a user

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.

More details

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

Rate this page: