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.
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.
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.
From Jun 30, 2025, the nodejs18.x runtime will be deprecated, impacting app deployments.
You must update your apps to use the newer nodejs20.x or nodejs22.x runtimes.
This is due to the Node.js version 18.x end-of-life scheduled for Apr 30, 2025.
We’re happy to introduce two new Jira Forge product events:
Component deleted - avi:jira:deleted:component
Issue type deleted - avi:jira:deleted:issuetype
Follow the links to read more about them.
Forge’s native Node runtime now supports Node 22.
To use this runtime, set your app.runtime.name to nodejs22.x in the manifest file.
We've added a new command forge eligibility that allows you to check the eligibility of your Forge app against predefined programs, such as Runs on Atlassian.
You can also check the eligibility of previous major versions of your app by using the --major-version flag.
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’re introducing a new program Runs on Atlassian as a Preview on Forge.
The program helps customers identify Forge apps that have no data egress and use data residency-enabled storage on the Atlassian Marketplace via a Runs on Atlassian badge.
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.
Eligibility requirements may change leading up to the launch of the program.
The forge lint and forge deploy commands will now output filename, index, line, and column numbers (if available) when an error occurs during compilation.
UI modifications, the Forge module that allows apps to modify fields, now supports the cascading select field on the Global issue create view.
For more information, see the list of supported fields for Global issue create.
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.
We're announcing a preview of rich-text bodied macros for Forge, allowing apps to define Confluence macros with a body in their manifest.
This also allows Connect apps to migrate their rich-text bodied macros to Forge.
Get started by checking out the macro module reference, or our tutorial on using rich-text bodied macros.
Rich-text body macros let users insert rich content, like images and tables, within a macro using the Confluence editor. Apps can access and render this content within their macros. Macros using a custom editor can also provide an initial macro body on the first macro insert.
To be able to deploy these changes to your manifest, you will need the latest version of the Forge CLI. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
To learn more about migrating Connect macros to Forge, see https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-macro/.
We’re announcing a preview of custom config editors for Forge macros, allowing you to use a UI Kit or Custom UI resource for your macro’s configuration experience.
This gives you greater control over the presentation of configuration to the user and more flexibility with the storage of configuration properties.
Get started by checking out the macro module reference, or our tutorial on adding custom macro configuration.
The custom macro configuration will be rendered in a modal overlaying the page, offering a larger canvas for more complex configuration scenarios.
Macros using a custom config editor can also provide an initial macro body on the first macro insert.
To be able to deploy these changes to your manifest, you will need the latest version of the Forge CLI. Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
Developers can now view timestamps in the developer console according to their local timezone, as set in their device's operating system. This update allows developers to easily correlate incidents and activity with their specific time zone.
Previously, all timestamps were displayed in UTC. Developers can switch between their local time zone and UTC via the Profile menu in the top-right corner of the developer console.
oAuth access token max TTL has been extended from 1 hour to 4 hours.
Developers can configure scheduled triggers to periodically deliver new access tokens with a longer expiry time of 4 hours. These tokens can then be cached for later use to authenticate requests with Atlassian APIs.
Read more here, or have a look at our documentation.
We added a new --major-version option to the forge deploy command in Forge CLI version 10.2.0. This option allows you to deploy minor upgrades to a specific major version of your app. Minor upgrades are automatic, and don't require any action by users or site admins.
This enhancement lets you backport minor version updates to sites running older major versions of your app (without manual intervention). This includes sites on all environments, including production.
For more information, see Backporting.
Rate this page: