This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
See what's next for Forge on our platform roadmap.
We're excited to share that Forge, our app development platform for Atlassian cloud products, is now generally available. You can rely on Forge's hosted infrastructure, storage, and FaaS functions to support apps in production; all of which are backed by Atlassian's operational readiness. Learn more about building the next Marketplace hit with Forge.
Note that some functionality in Forge remains in beta while we're still making changes that may break your apps. Learn more about the current functionality in beta.
This is a reminder about the changelog announcement regarding the deprecation of the Forge sandbox runtime on Aug 28, 2024.
The retirement of the sandbox runtime will take effect on Feb 28, 2025, upon which any apps using the sandbox runtime will stop working.
Please ensure you update your app before the Feb 28, 2025 using this guide.
If you have questions or concerns about this deprecation, please visit this community thread.
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/.
Option to relink data after app reinstallation is now being considered as a future improvement to the developer platform. If this is of interest watch this roadmap item for updates. See https://ecosystem.atlassian.net/browse/ROADMAP-107 for more information.
The @forge/api package has historically used node-fetch as the underlying HTTP client for making network requests. As of version 5.0.0, @forge/api will start using undici as the underlying HTTP client.
This change should fix the occasional occurrences of ECONNRESET errors (bug report).
Previous versions of @forge/api suffered from occasional ECONNRESET errors due to a bug in the way in-built https (which node-fetch depends on) manages keep-alive connections.
Moving to undici will also allow @forge/api to drop its node-fetch dependency (which has been requested here). However, in this version, node-fetch is still a dependency as we require it for a fallback mechanism. It will be removed shortly once the undici implementation is stable.
Note that this is a major version bump. The API interface has been slightly adjusted to support undici as the underlying client. For most use cases, this will not change anything, but if you depend on specific node-fetch types (e.g - you construct a node-fetch Request object which you pass in as the request) then this will no longer work.
The hard dependency on the cloudflared package installation alongside the Forge CLI has been removed. This helps unblock customers who were previously unable to install the Forge CLI due to this dependency.
In Enterprise environments, sometimes the installation of the cloudflared package associated with Forge CLI may be blocked by network administrators.
This outbound connection is required for the proper functioning of the Forge Tunnel. For more information, please refer to the documentation.
The Forge Tunnel will now attempt to use any locally installed version of cloudflared if it is blocked or unavailable with the Forge CLI. This change allows users to install and utilize the Forge CLI, even if tunneling is affected by the availability of cloudflared.
Install Forge CLI version 10.13.5 or later to use this functionality.
The contextAri field is now optional on all Storage GraphQL queries and mutations. Forge now directly determines the value of this field from the app installation.
The contextAri field used to be associated with the context where a Forge invocation is being performed. It was assembled by concatenating 'ari:cloud:confluence::site/' with context.cloudId obtained from the Forge Invocation Token.
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/.
The navigate and open methods from the @forge/bridge router API now allow you to programmatically navigate to select locations using a NavigationLocation object instead of a URL.
This capability is in Preview and is supported across Jira and Confluence modules for both UI Kit and Custom UI.
For more information on the NavigationLocation object, refer to the router documentation.
Update to the latest version of @forge/bridge with npm install --save @forge/bridge@latest
As per CHANGE-1787 from Jul 8, 2024 , the author and updateAuthor fields of Worklog are no longer mandatory for the issue worklog created and issue worklog updated product events.
Until now, the first version of an app to adopt Forge features or migrate fully to Forge required admin approval in order to be upgraded on an existing installation site.
Connect apps moving to Forge can opt-in to have their existing Connect installations updated to their latest Forge version, as long as they do not have an elevation in permissions. The rollout will be staggered over 96 hours by default, but can be further staggered via the staged migration process.
Instructions on how to opt your app in to this feature and check its eligibility can be found at Minor version updates (Connect to Forge) (Preview).
Forge SQL is now available in Preview. This release provides improvements to database provisioning, performance, and observability.
Please review the available documentation to get started with Forge SQL, including assessing all of the current limitations of the service.
The Preview version of Forge SQL currently does not support data residency. By using Forge SQL, you acknowledge that Section 6 (Data Residency) of the https://developer.atlassian.com/platform/forge/developer-terms/ does not apply to data stored using Forge SQL, and you must not use Forge SQL for any applications that require data residency.
The Rovo agent and action modules are now generally available.
Get started with the Build a Rovo Agent hello world app tutorial.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-83-live-docs-pages-in-confluence-cloud/88495
Rate this page: