This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
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.
To ensure compliance with Atlassian's branding guidelines, we are rolling out a hard block starting December 31, 2024, for existing apps with unresolved naming violations. Learn more here. Partners with open tickets related to app name violations must address these issues by this date. Failure to do so will render their app names non-compliant under Atlassian's brand guidelines. We have been sending reminders and will continue to provide updates and support to help you transition smoothly before the deadline.
Key Updates and Timelines:
Hard Block for Current Apps with Violations:
A hard block for existing app names with violations will take effect on December 31, 2024. All apps must be updated to comply with the guidelines before this date.
Soft Block for Existing Apps:
As of October 29, 2024, a soft block has been in place for existing apps with naming violations. Partners receive warnings during app version or name updates, but updates are not currently blocked.
Hard Block for New Apps:
Effective October 29, 2024, all new apps must comply with updated branding guidelines. Non-compliant app names are not accepted for approval submissions.
We appreciate your cooperation as we work together to maintain a consistent and fair Marketplace.
Bitbucket Data Center and Server 8.9.23, 8.19.13, and 9.4.1 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
What’s new in Confluence 9.2 LTS?
9.2 is a Long Term Support release. Learn more
Refine your ATST license limit health check alerts from the UI
To learn more, see Confluence 9.2 Release Notes.
This GA release was made available on 10 December 2024.
This release doesn’t support Server licenses. If you have a Server license, check out your options for upgrading.
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.
The non-public endpoint /rest/teams/1.0/teams/find will be removed as part of the changes coming to Teams. This change is necessary to streamline our API offerings and improve performance. This change will take effect 3 months from this notice 05 Mar 2025.
If you have integrations with this internal API endpoint, migrate your system to use the teamSearch GraphQL query instead.
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/.
Rate this page: