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 apps, 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.
Forge CLI now supports listing recent deployments using a new command, forge deploy list.
This command, by default, will show a table of the app’s recent deployments sorted by deployment date. It includes relevant details, including the environment and version, as well as the new “build tag” if the deployment was made using the forge build command. It also supports JSON output using the --json option, similar to other list commands in the Forge CLI.
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 build a custom Teamwork Graph connector using Forge is now in EAP. Connectors allow you to ingest your app data into the Graph, associate it with Atlassian objects (for example, work items), and make the data available to customers in platform experiences like Chat, Search and Agents.
If you’re interested in joining the EAP, we recommend first checking the supported object types to see if we support your use case. Support for custom object types will come in a future release (2026).
To participate, please sign up for the EAP here.
The Forge CLI is now available via a development container for both VS Code and IntelliJ. It provides a consistent and isolated environment that is pre-configured with the necessary dependencies to build Forge apps.
To get started, follow this guide to install the necessary tooling and set up your environment.
We’re adding the capability to uninstall and upgrade Forge apps directly within your Bitbucket workspace settings. This means you no longer need to do these tasks in the Distribution screen of the developer console.
Note, the upgrade functionality is only available if the app has a more recent version available.
The Forge https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-panel/ module now supports options to show or hide a panel in all work items throughout a project.
These options dynamically appear in the panel’s action menu, depending on whether the panel is hidden or displayed in all work items. The action menu will show the Show for all work items option if the panel is hidden on all or some work items. Selecting this option will replace it with the Hide from all work items option. Both options will show/hide the panel on all work items throughout the project.
We’ve added new Confluence product events for entity deletions:
avi:confluence:deleted:page
avi:confluence:deleted:blogpost
avi:confluence:deleted:attachment
avi:confluence:deleted:custom_content
avi:confluence:deleted:space:V2
You can use these events to invoke your Forge app function when a page, blog post, attachment, custom content, or space is deleted. For more details see the Confluence events reference documentation.
As part of our Runs on Atlassian program, we aim to continue enforcing a high level of trust in the signal and its definition.
As such, we are limiting what Forge developers can include in the analytics category of the external permissions section of their manifest. Specifically, from Aug 19, 2025 , you cannot use analytics tools that don't capture analytics data.
In addition, from Sep 16, 2025, you will no longer be able to use analytics tools that do not comply with the Analytics tool policy for Forge apps. We’ll announce the enforcement of the policy in a separate changelog.
Using a domain outside of this allowlist will prevent your app from deploying:
1
2
3
4
5
Error: Manifest validation failed: The value of the analytics egress is not a supported domain
Additional information: {
"address": "*.example-dev.com",
"support": "To review the Analytics tool policy, go to: https://go.atlassian.com/forge-analytics-egress-support"
}
If you need to use a domain that isn’t on the allowlist, please raise a support ticket.
Following our previous announcement, eligible apps migrating from Connect to Forge will now automatically roll out to customers. Rollouts will occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.
Apps which have previously adopted Forge from Connect and have not opted in to minor updates will be progressively migrated in the coming weeks.
See https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-forge-updates-preview/ for details about eligibility. To test and validate your app’s migration process, you can still opt-in to the staged migration process.
We’ve added new Confluence product events for custom content:
avi:confluence:created:custom_content → Triggered when a new custom content is created
avi:confluence:updated:custom_content → Triggered when a custom content is updated
You can use these events to invoke your Forge app function when custom content is created, updated for an entity. For more details see https://developer.atlassian.com/platform/forge/events-reference/confluence/#labels.
Enhancements to usage metrics and removal of data-at-rest information
We're making changes to our usage metrics to enhance data accuracy and reliability. This update ensures that developers receive the most precise data possible, allowing for better insights and decision-making. Additionally, we're removing the data-at-rest usage information due to unreliable metrics and to simplify our backend infrastructure.
There are no immediate actions required from developers regarding the enhancements to usage metrics.
Forge macros are now supported in Confluence Query Language (CQL).
Previously CQL field macro only supported core macros but now can also search for forge macros with the same syntax: macro="decision-macro"
If multiple macros have the same key, it will match pages that have any of them. To match on only one macro you can include its appId: macro="d31527a9-9b37-4734-916a-eb6170e5e701/decision-macro"
Forge now supports migrating custom content modules from Connect to Forge while preserving existing content. Add the migratedFromConnect: true to your custom content module to maintain compatibility with existing Connect content.
See the documentation for more details.
Forge offline user impersonation was recently made available in Preview. As part of this, the ability to exchange a Forge system OAuth token on a Forge remote for a token to impersonate any user.
This was released with a rate limit of 10,000 requests per minute per app, however after carefully consideration, we need to temporarily reduce this limit to 1,000 requests per minute per app. This rate limit applies only to the exchanging of a system token for a user impersonation token using the offlineUserAuthToken GraphQL mutation. Calls from a Forge function using asUser are not affected. Calls made to APIs using these tokens are not affected and instead use the rate limit defined for each API endpoint
We will continue to work towards increasing this limit as we move towards general availability of this feature.
To address parity gaps between Connect webhooks and Forge product events in Confluence, the following changes have been made for various events:
Change category | Forge product events (New) | Connect webhooks (Existing) | Affected events |
|---|---|---|---|
Event Timestamps |
|
| All events |
Notification control |
|
| Events that support notification suppression |
Update triggers |
|
| All update events |
Content versioning |
|
| All content, comment and attachment events |
Creation history |
|
| All content and space events |
Creator information |
|
| All content and space events |
Ownership |
| N/A | All content events |
Container metadata |
| Various fields representing a container | Attachment, comment, custom content events |
The space.homepage field hasn’t been added to space events due to an unexpected issue. We will add it as soon as we resolve the problem on our end. However, the ID of a space homepage can still be retrieved via the https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-space/#api-group-space.
For more details on the Forge product events, refer to https://developer.atlassian.com/platform/forge/events-reference/confluence/ page.
The nodejs18.x runtime available to Forge apps has reached the end of its deprecation period, and is no longer supported.
Apps using this runtime can no longer be deployed or updated, although existing deployed apps may continue to function. Such apps are provided “as-is", with no warranties or access to support. Over time, unsupported runtimes may become non-functional or vulnerable to security issues.
All app developers are strongly encouraged to update their app to a supported Node.js runtime (nodejs20.x or higher) as soon as possible.
Rate this page: