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.
App developers can now use the connectToForgeMigration manifest module to share their Connect to Forge migration plans and commitment status with Atlassian and their users. This experience is currently limited to developer canary tenants with private apps.
Apps with public Marketplace listings will remain unaffected. However, we encourage you to add this module to your production app, so you can receive the updated behaviour as soon as it goes live.
Please see documentation here.
This module should be added to every major version of your app. It is available for apps extending Jira and Confluence.
Going forward, the blanket classification of all updates as major version updates is being replaced with a per-app policy based on each app's migration status.
Apps that have completed the Connect-to-Forge transition: Any app whose latest deployed version contains only Forge modules and scopes -with no remaining Atlassian Connect modules - will be re-enrolled into minor version updates once that version has been released. The proportion of the install base that has upgraded to the latest version is not a factor; what matters is that a bulk-upgrade path existed from the last version that included Connect modules to the current Forge-only version.
54 apps that already meet this criteria have been moved back to minor version updates, and we will be refreshing that list on a weekly cadence.
Apps that have not yet completed the transition: Apps that still include Connect modules in their latest deployed version will not be able to use minor version updates indefinitely. This measure protects platform stability by ensuring that API traffic from these very large apps continues to be managed through controlled rollouts rather than automatic minor-version upgrades.
Backporting changes to older major versions (temporarily restricted)
For now, you can’t publish updates to earlier major versions. This temporary restriction is in place for the same reason large apps were moved to controlled rollouts: to prevent large, high-impact changes from being automatically applied to a significant number of customers and to protect platform stability.
If you need to backport a fix to an older major version, we may be able to make an exception on a case-by-case basis. Please reach out to Atlassian with the app details, the version you need to backport to, and the rationale for the change.
As always, this policy has no effect on how apps qualify for the Forge revenue share rate. Your latest deployed app version determines revenue share eligibility.
For detailed information on how to use forge version bulk-upgrade, see https://developer.atlassian.com/platform/forge/cli-reference/version-bulk-upgrade/.
Please see the previous change here: https://developer.atlassian.com/changelog/#CHANGE-3141
A back-end change required to safely re-enable minor version updates is in the process of being rolled out. As a result, all updates to Forge apps with over 50,000 users continue to be classified as major version updates.
Please continue to use the forge version bulk-upgrade command to roll out updates to customer sites until further notice. We expect to have this change out the door soon. Please do not rely on minor version updates until the next changelog announcement confirms that it is safe to do so.
Atlassian will discontinue support for the Atlassian Connect Express (@atlassian/atlassian-connect-express) and Atlassian Connect Spring Boot (atlassian-connect-spring-boot) frameworks alongside the end of support for the Atlassian Connect platform.
As of April 30, 2026, Atlassian has ceased development of new features for these frameworks. While we will continue to patch vulnerabilities and assess bug fixes on a case-by-case basis for the time being, this support will end completely when the Connect platform enters its final EOS phase in Q4 2026. When that happens, Atlassian will no longer:
Investigate or remediate breaking changes caused by product or platform updates.
Provide official maintenance or security patches for these frameworks
Both frameworks will remain available as open-source projects under the Apache 2.0 license, and their source code will continue to be accessible at:
Atlassian Connect Express: https://bitbucket.org/atlassian/atlassian-connect-express
Atlassian Connect Spring Boot: https://bitbucket.org/atlassian/atlassian-connect-spring-boot
Developers who wish to continue using these frameworks can fork and maintain them independently. However, any future maintenance (including addressing breaking changes or security issues that arise after Connect enters EOS) will be the responsibility of the community or individual developers.
For details on the Atlassian Connect EOS timeline and phases, see:
https://www.atlassian.com/blog/developer/announcing-connect-end-of-support-timeline-and-next-steps
The rovo:agentConnector module allows you to integrate remote AI agents hosted on external infrastructure into Jira. Once registered, users can interact with remote agents in a similar manner to other users and Rovo agents—they can be assigned work items, @mentioned in comments, and chatted with via the Rovo Chat panel.
Use this module to integrate Jira with AI agents residing outside of the Atlassian platform (such as GitHub Copilot, Cursor Background Agents, or Box AI Agents).
To join the Early Access Program, complete the sign-up form.
For more information, see the rovo:agentConnector module documentation.
Participation in the EAP is subject to limitations or eligibility requirements.
Following the EAP release, fullscreen viewport modals and the view.onClose() method is now generally available (GA).
You can use the fullscreen viewport for macro custom configuration modals, and for the UI Kit Modal component and Custom UI bridge Modal API in Jira and Confluence. UI Kit modal body component padding can now be toggled with hasInlinePadding prop and Custom UI bridge Modal padding has been removed.
Upgrade to the latest version of @forge/cli to start building with the fullscreen viewport and view.onClose() method.
For more information, see the documentation for the UI Kit modal, bridge modal, macro and view.onClose() method.
Starting Jul 28, 2026, Atlassian will no longer support allowlists for Statsig or LaunchDarkly tools in Runs on Atlassian (ROA) Forge apps.
This change is part of our effort to streamline feature management and ensure the security and performance of apps running on our infrastructure.
What you need to do
If your app currently relies on Statsig or LaunchDarkly allowlists, you must migrate to the native Forge feature flag capability before the deprecation date.
Review the Forge feature flags documentation to understand how to implement native flags.
Update your app code to use the Forge Feature Flags SDKs instead of external providers.
Test your app in a development environment to ensure feature flag logic works as expected.
Deploy your updated app before July 28, 2026.
We’re introducing a new Forge License REST API which lets Forge apps retrieve license information for themselves or for other apps owned by the same developer space.
You can now transfer private apps yourself between developer spaces where you're an admin in both, directly from the developer console — no support ticket needed.
To transfer a private app to a space where you're not an admin, or to move a Marketplace app between spaces, you'll still need to open a support ticket.
For more details, see the documentation.
In line with the CLI version deprecation policy, Forge CLI versions 12.8.0 and earlier will no longer be supported from May 11, 2026.
From this date, these CLI versions will stop working. To reduce the risk of failure, we recommend upgrading to the latest supported Forge CLI version.
Action required
Run the following command to install the latest version of the Forge CLI: npm install -g @forge/cli@latest
We’re announcing the deprecation and upcoming decommission of the AUI CDN.
AUI CDN will be shut down after Oct 30, 2026.
What is AUI CDN?
aui-cdn.atlassian.com hosts legacy JavaScript and CSS assets for AUI (Atlassian User Interface) versions 5.2.0 – 6.0.9.
Who is affected?
The AUI CDN is primarily used by Connect apps, so this mostly affects apps not yet migrated from Connect to Forge. Connect has announced its own End of Support late 2026. In some rare cases, AUI CDN is also used by Forge apps.
How to check if you're affected
Search your app's source code for any URLs containing aui-cdn.atlassian.com. If you find any references, your app is loading assets from AUI CDN and you need to take action before the shutdown.
What to do if you're affected
Remove all references to aui-cdn.atlassian.com from your codebase and migrate to a supported alternative:
Recommended: Migrate AUI to Atlassian Design System or Forge UI Kit. Any Atlassian Connect apps should also migrate to Forge, as Connect End of Support has been announced.
If migrating is not suitable for you (e.g. non-React apps), you have these options:
Bundle AUI directly: via npm. See the AUI documentation.
Third-party CDN: use a CDN that serves npm packages, e.g. jsDelivr (https://cdn.jsdelivr.net/npm/aui@latest/) or unpkg (https://unpkg.com/aui@latest/)
Self-host: download any required AUI assets and serve the static assets yourself
Timeline
AUI CDN will be shut down after Oct 30, 2026. After this date, any requests to aui-cdn.atlassian.com will fail, which will break apps that haven't migrated. Please migrate as soon as possible.
The license objects in app context and FIT have a new active property indicating whether the app license is active. The existing isActive property is still provided but is now deprecated and will be removed after Oct 17, 2026.
This will make the license object the same across function context, App Context, Forge Invocation Token, resolver context, and the UI context.
Following its initial Preview release, Forge Realtime does not require the read:app-global-channel:realtime scope to use global channels.
Impact: No behaviour change for apps already deployed or installed with this scope.
Action required: Please remove the read:app-global-channel:realtime scope from your app manifest. This scope will be removed on 18 May 2026, and any app manifest that still includes it will be blocked from further deployment after that date.
Removing this scope will cause your next app version to be a major update. You can use the version bulk-upgrade command to move existing installations to the new major version.
We've added a new Confluence Forge event for performed search: avi:confluence:performed:search
You can use this event to invoke your Forge app function when a Confluence search is performed. For more details, see the Confluence events reference documentation.
Rate this page: