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 its preview release back in February, Adopting Forge from Connect is now generally available.
The majority of apps can now incrementally adopt Forge with their existing Connect apps. The remaining apps will be able to do so when Data Residency support is available for Forge Remotes.
Learn more in our blog post - Connect apps will gain new extensibility features through Forge
Existing Connect apps now have a simpler, automated and incremental pathway to adopt Forge capabilities. This release includes:
Automated tooling to support the conversion from Connect to Forge
Support for immediate version updates of Forge apps containing connectModules
Increased compatibility for the types of connectModules that can be declared within a Forge manifest
Support for Forge Remote Compute (preview) in the Atlassian Connect Express (ACE) and Connect Spring Boot (ACSB) frameworks.
You can now migrate existing Connect macros to the native Forge macro module.
This change allows your app to render existing Connect macros in Confluence pages as Forge macros, when you adopt a Forge macro with a key matching the Connect macro.
See Migrate a macro module from Connect to Forge to get started.
Following the EAP release, we are excited to announce that the Rovo Agents and action modules on Forge are now available in Preview. This means they can be used in production environments.
For more information on Forge and Rovo, see :
The Rovo product is in a closed early access program. If you require access to Rovo for development purposes apply for access to the Rovo developer EAP.
See our Preview policies documentation for more information.
From Sep 6, 2024 , the App Migration Platform can handle Forge App Migrations originated from P2 plugins (server/data center)
Please check our updated docs. And in case you have previous experience with P2 to Atlassian Connect migrations, we have a special page highlighting the differences between the two.
You can now filter for versions when filtering app logs via the More filters dropdown. This helps narrow down log results based on the selected major versions.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-63-page-extension-in-editor-design-changes-and-more/83196/1 .
We are excited to announce the improved alerting experience in the developer console as part of Forge’s Early Access Program (EAP).
This new feature allows app admins to create granular alert rules based on specific metrics with customizable filters, conditions, and responders to focus on issues that matter most. Alert rules can be configured based on invocation count, invocation errors, and invocation success rate.
By participating in the EAP, you can:
Receive notifications for the metrics that matter most to you and your team.
Configure thresholds and conditions to control the volume of alerts.
Tailor responders so that the right team members get notified about alerts.
To learn more, see Alerts (EAP). To participate in this EAP, sign up using the Forge improved alerting EAP form.
We’ve updated the flow of the forge deploy command in the Forge CLI, where a name for the default DEVELOPMENT environment is no longer suggested. We’ve also updated the documentation to reflect this change accordingly.
UI modifications, the Forge module that allows apps to modify fields, now supports the status field on the Issue view.
If your app uses granular scopes, it will need the following permission to access this field:
read:issue-status:jira
For more information, see the list of supported fields and read about granular scopes.
We’ll soon be modifying the functionality of the forge logs -n <limit> and forge logs --limit <limit> CLI commands. Instead of showing logs from the last <limit> invocations, it will show the last <limit> log lines. This change will take effect on or after Oct 31, 2024.
This is a non-breaking change. While the behavior of the -n argument is changing, existing setups will not be affected.
Requests to your remote backend now include the license data of the app within the Forge Invocation Token (FIT).
Any apps using UI Kit @forge/react version 9 will stop working from Nov 28, 2024 (3 months post this announcement).
To support your upgrade, please use the following guide:
Any apps using UI Kit 1 will stop working from Feb 28, 2025 (6 months post this announcement).
To support your upgrade, please use the following guide:
Forge’s legacy runtime is now deprecated, and will be removed in 6 months. This means:
From Oct 29, 2024: Forge apps that haven't been updated since January 1, 2023 will no longer function.
From Feb 28, 2025: All Forge apps still running on the legacy runtime will no longer function.
Apps created and last deployed before April 17, 2024 may still be running the legacy runtime. For details about migrating your app to the latest runtime, see Upgrading from legacy runtime.
We strongly recommend that all apps run the latest runtime, as it offers several advantages over the legacy version:
The latest runtime runs in a standard Node.js 18 or Node.js 20 environment, and will also support newer versions as they become available. As such, you can import any built-in, local, or third-party Node modules into your app. This provides compatibility with all Node libraries and NPM packages, allowing you to leverage the entire JavaScript developer ecosystem.
The legacy runtime runs in an environment that mimics Node.js 14. Only a subset of Node.js functions are supported, making some third-party packages incompatible with it.
The legacy runtime employs a v8 JavaScript isolate sandbox initialized for each invocation. In contrast, the latest runtime operates directly within a secure VM environment, enhancing both the speed and security of invocations.
The legacy runtime offers 128MB of memory per invocation, while the latest runtime provides 512MB.
We have made improvements to Key-value and Custom-Entity store to now return up to a 100 query results per page compared to 20 previously. Please note that the default number of results returned will still stay the same at 10 query results per page.
Rate this page: