Rate this page:
This changelog is the source of truth for all changes to the Forge platform that affect people developing Forge apps.
Posts are made in the Forge announcements category of the developer community when the changelog is updated. Subscribe to the Forge announcements category to get notifications.
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.
We’ve removed support for the Text component format property <Text format="markdown">. This removes Markdown support. Apps using markdown must be upgraded immediately to UI kit version 0.9.0 or later, as they are at risk of breaking.
Run npm install @forge/ui@latest on the command line to install the latest version of UI kit.
We implemented a NodeJS crypto module polyfill in the Forge runtime. This polyfill includes support for secure random number generation.
We’ve modified the Referrer-Policy header used by custom UI resources to be less restrictive, from no-referrer to strict-origin-when-cross-origin.
Display conditions are now available for the Confluence byline item module. Using display conditions, you can control the visibility of your app modules in the UI. See the display conditions reference documentation for more details.
Run npm install -g @forge/cli@latest on the command line to install the latest CLI version with linting for display conditions.
We’ve restructured the Modules and UI kit components reference documentation, to make it easier to navigate and consume content.
forge install --upgrade now shows all newly added permissions in the requested installation upgrade.
This fix corrects the custom UI bridge requestJira and requestConfluence methods when generating content types for form-data. This fix enables attachments to be sent successfully to REST APIs which accept multipart/form-data content.
Run npm install @forge/bridge@latest in your resource directory to install the latest version of Forge bridge.
This release includes:
A fix for the linter not detecting missing scopes for Confluence REST API calls.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
We’re adding new APIs to the existing Forge Storage API so that Forge apps now store secrets and credentials securely.
Similar to storage.set, storage.get and storage.dete, the new APIs are storage.setSecret, storage.getSecret, and storage.deleteSecret.
Added Custom UI support for defining the editing experience for Jira custom fields and Jira custom field types.
Added Custom UI support for Jira context configuration of custom fields.
Added a submit method to the view export of the @forge/bridge package to enable form submission. The method is supported in Jira custom field edit, Jira custom field type edit, and Jira context configuration.
To help support developers moving Connect apps to Forge, we have added linter support for the connectModules property to the Forge CLI.
We've modified the forge install --upgrade warning to communicate specifically when the upgrade requirement is caused by permission changes.
Previously, to delete an app, the app must be uninstalled from all sites on which it was previously installed. Now, you can raise a ticket with the Atlassian Marketplace team, for the team to handle the uninstallation and deletion of the app for you.
Learn more about deleting Forge apps and retiring apps from the Atlassian Marketplace.