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.
Following the Preview release, the Frame component in UI Kit is now generally available (GA).
The Frame component allows you to load custom resources within UI Kit, making it easy to import non-UI Kit components in a UI Kit module.
There are no changes required for developers currently using the Frame component. For more information on how to use the Frame component, see here.
Following the deprecation announcement on 28 Aug 2024, we have now removed UI Kit 1 from the Forge platform.
For apps still using UI Kit 1, customers will see that their app version is outdated due to a deprecated platform component.
You will need to upgrade to the latest version of UI Kit for your app to work. If you are in the process of upgrading your UI Kit 1 app, please refer to these resources to guide you through the transition:
Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below. Action will be required from developers using deprecated extension points.
deprecation notice Deprecating a subset of Confluence page extension points.
UPDATE, 02 Mar, 2025 The scheduled upgrade was successfully performed on March 02, 2025 between 12:30 AM to 03:30 AM UTC, and we have verified that all the capabilities mentioned below are working as expected. If you are experiencing ongoing issues with these capabilities please contact your local Atlassian site administrator. If you need further help, please raise a support ticket at https://support.atlassian.com/#contact.
EDIT, 28 Feb, 2025 : Please note that below mentioned times are UTC i.e. 02 Mar, 2025 between 12:30 am to 03:30 AM UTC
Forge platform will be undergoing maintenance on March 02, 2025 between 00:30 AM to 03:30 AM. During this interval, below capabilities will not be available intermittently:
Create/update/delete apps
Deploy apps
Install/uninstall/upgrade apps
View existing installations
App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.
We've added a new command forge version that lets you check for the major version history of any app at any time. You can also use this command to do the following:
View the details of specific major versions, as defined in the manifest
Compare the details of two major versions
This new command can help you in checking and maintaining the eligibility of your Forge app against predefined programs, such as Runs on Atlassian.
To know more about the Runs on Atlassian program, visit https://go.atlassian.com/runs-on-atlassian.
To check if your app is eligible for Runs on Atlassian, go to the Forge CLI documentation.
We’ve added a new Bitbucket Forge product events: avi:bitbucket:created:commit-comment. You can use these events to invoke your Forge app function when a commit comment is created. For more details see https://developer.atlassian.com/platform/forge/events-reference/bitbucket/.
The webtrigger and uninstall Forge CLI commands no longer support the installationId positional argument. To specify an installation context, use the command flags for environment, site and product instead. For example:
forge webtrigger --site mysite.atlassian.net --product Jira --environment production
See https://developer.atlassian.com/platform/forge/cli-reference/webtrigger/ and https://developer.atlassian.com/platform/forge/cli-reference/uninstall/ for more details.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli and receive these changes.
The ability to delete Custom Entity indexes is now generally available to all developers. With this capability, you can remove indexes from an existing entity in your manifest and deploy the change to adevelopment or a custom environment.
Note that Custom Entity indexes that have already been deployed to production or staging can no longer be deleted in any environment.
The Forge CLI and other associated JavaScript packages are published for public consumption to the npm Registry (eg. https://www.npmjs.com/package/@forge/cli ).
Due to an oversight, these packages were published with metadata declaring that the packages are UNLICENSED. This is incorrect; usage of the Forge CLI and other parts of Forge are governed by the https://developer.atlassian.com/market/atlassian-developer-terms.
This issue has been fixed. Packages published to the npm Registry under the @forge scope now correctly identify license terms associated with the usage of Forge.
All public packages for Forge will now declare the following license:
1Copyright (c) 2025 Atlassian
2Permission is hereby granted to use this software in accordance with the terms
3and conditions outlined in the Atlassian Developer Terms, which can be found
4at the following URL:
5
6https://developer.atlassian.com/platform/marketplace/atlassian-developer-terms/
7
8By using this software, you agree to comply with these terms and conditions.
9If you do not agree with these terms, you are not permitted to use this software.
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.
To increase awareness of the impending deadline, apps using the sandbox runtime will be blocked from executing in all development environments beginning Feb 19, 2025.
If you have questions or concerns about this deprecation, please visit this community thread.
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/.
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.
Rate this page: