Changelog

We’re excited to announce that you can now declare a static or dynamic response type for the web trigger module. This will allow more apps to be eligible for the Runs on Atlassian program.

You can read more about the new schema and how to configure these response types in the Web trigger documentation.

Developers can now easily search for required log lines by using the "Add to search" button next to the log details you want to filter by, such as Invocation ID, Trace ID, Function, and Site. This allows you to directly incorporate the values from the log lines into your search, making it easier to refine and filter results more quickly.

We’ve implemented a REST API gateway that remote services can use to access Forge’s Key-Value Store (KVS) and Custom Entity Store. The REST API provides an interface that is simpler and more performant than the existing GraphQL API gateway.

We will continue supporting the GraphQL API gateway. However, all future KVS and Custom Entity Store updates will be only be available through the REST API. If you are planning to integrate Forge hosted storage into a remote service, we recommend that you use the REST API gateway instead.

See Accessing Forge storage from a remote via REST API for details.

We’ve released a new package named @forge/kvs (it is stable and ready to use), which will provide access to all native Key-Value Store (KVS) and Custom Entity Store capabilities moving forward. We aim to keep this package in sync with its corresponding REST API gateway, ensuring consistency between both native and remote implementations.

Legacy versions of the KVS and Custom Entity Store were provided through the storage module of the @forge/api package. We will continue supporting this module. However, all future KVS and Custom Entity Store updates will only be built on modules in the current @forge/kvs package.

Transactions for Forge KVS and Custom Entity Store is now available in EAP.

This feature allows multiple operations in a single transaction, ensuring that all operations are either committed or rolled back together if one fails. When used in the Custom Entity Store, you can add conditions to operations.

Refer to the Forge documentation for KVS and Custom Entity Store for more information about this new capability.

To sign up for this EAP, use the request form.

We've released a new major version of @forge/react for UI Kit apps. This update includes enhancements to the useConfig hook, improving performance in macro config apps when receiving configuration value changes. The enhancement supports macro config apps that use the useConfig hook to obtain the latest updated configuration values through standard React component re-renders instead of re-mounting the app.

• Confluence macro config apps using the useConfig hook should upgrade to @forge/react version 11.0.0 for improved performance.

• Confluence macro config apps using the useProductContext hook or view.getContext() method need to transition to the useConfig hook before upgrading in order to properly access the latest values after the configuration updates.

• There will be no impact on apps using @forge/react major version 10 or older, however they will not gain the latest performance enhancements.

In the latest version of @forge/react, we're adding a new disableSubmitOnEnter property to the UI Kit Jira component, CustomFieldEdit. The property can be used to disable the submission of the field value when the “Enter” key is pressed.

For more information on this component, see the component documentation.

Forge Remote Data Residency realm migrations is now available in Preview. This release provides apps with the ability to support customer-initiated migrations between data residency regions.

Please review the documentation to learn more about how to support realm migrations in your app.

Connect apps moving to Forge can opt-in to have their existing Connect installations updated to their latest Forge version, as long as they do not have an elevation in permissions. The rollout will be staggered over 96 hours by default, but can be further staggered via the staged migration process.

Until now, the first version of an app to adopt Forge features or migrate fully to Forge required admin approval in order to be upgraded on an existing installation site.

There are no changes in how updates work for apps that do not opt-in to this functionality.

Instructions on how to opt your app in to this feature and check its eligibility can be found at Minor version updates (Connect to Forge) (Preview).

Live docs are coming to Confluence Cloud as new content type alongside existing Pages. Live docs can be updated instantly without having to publish, allowing teams to quickly collaborate on content. All sites in the Developer Canary Program have access to Live docs (as of November 2024).

We are asking developers to test their apps in Live docs and make sure that they are functioning as expected by May 30, 2025.

See more technical guidance on Live Docs in our developer community post here. We are also working on including all details in official documentation on developer.atlassian.com where relevant, but wanted to share with developers ahead of time.

Following the Preview release, the Frame component in UI Kit is now generally available (GA).

The Frame component allows you to load custom resources within UI Kit, making it easy to import non-UI Kit components in a UI Kit module.

Following the deprecation announcement on 28 Aug 2024, we have now removed UI Kit 1 from the Forge platform.

For apps still using UI Kit 1, customers will see that their app version is outdated due to a deprecated platform component.

You will need to upgrade to the latest version of UI Kit for your app to work. If you are in the process of upgrading your UI Kit 1 app, please refer to these resources to guide you through the transition:

• Example of migrating an app from UI Kit 1 to UI Kit

• Upgrade from UI Kit 1 to the latest version

• Upgrade to @forge/react major version 10

• Notify site admins using the Forge app with UI Kit 1

Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below. Action will be required from developers using deprecated extension points.

deprecation notice Deprecating a subset of Confluence page extension points.

Forge platform will be undergoing maintenance on March 02, 2025 between 00:30 AM to 03:30 AM. During this interval, below capabilities will not be available intermittently:

• Create/update/delete apps

• Deploy apps

• Install/uninstall/upgrade apps

• View existing installations

App invocations will continue to work for existing users of the apps. However, new customers might not be able to use apps as consent process will be impacted during this interval as well.

We've added a new command forge version that lets you check for the major version history of any app at any time. You can also use this command to do the following:

• View the details of specific major versions, as defined in the manifest

• Compare the details of two major versions

This new command can help you in checking and maintaining the eligibility of your Forge app against predefined programs, such as Runs on Atlassian.

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.