Changelog

As part of our new design language, the refreshed colors and components in the Atlassian Design System (that first launched in products at Team '25) are now officially in GA. Also included is a further tweak to accent token colors in hover/pressed states to improve accessibility.

What you need to do if you are using Forge Custom UI or Atlassian Connect:
Bump @atlaskit/tokens + relevant component packages to the latest version to align your app's look and feel with Atlassian apps.
What you need to do if you are using Forge UI Kit or Forge UI Kit 2:
Nothing! You should have the newest components by default.

The GET methods of the Key-Value Store and Custom Entity Store SDKs can now return optional metadata fields, namely:

• createdAt

• updatedAt

In the previous pricing announcement, the SQL Data stored metric used an average model with billing unit in GB. We are shifting to a sum/counter model. To prevent financial implications from this change, we are adjusting the billing unit, monthly quota, and pricing.

Starting today, the developer console and cost estimator will reflect this change. SQL data stored usage in the developer console will now be displayed in GB-hours.

With immediate effect, the Developer Console will display near real-time usage data for all chargeable capabilities. In rare cases, a delay of a few hours may occur before the latest usage appears.

The following Object Store UI components are now available for through Forge’s Early Access Program (EAP):

• UI Kit components:

  • File picker: allows the user to select files stored locally.

  • File card: displays information about a file (including name, type, and size); this can be used to managed selected files and displaying upload progress.

• Frontend components for integrating with the Forge Object Store via backend resolver:

  • useObjectStore hook method (for apps that use UI Kit)

  • objectStore bridge API (for apps that use Custom UI)

To start testing these capabilities, please go here.

The Batch operations capability is now generally available, allowing you to execute multiple KVS and Custom Entities requests simultaneously. These batched requests are executed in parallel, and each requests will be completed on a “best effort” basis (unlike Transactions, where all requests are completed in an “all or nothing” basis).

This capability was originally launched in EAP as Bulk Set; on Sep 3, 2025 we closed this EAP in preparation for general availability.

Batch operations is included in version 1.2.0 of the @forge/kvs package.

Following its EAP release, Forge Realtime is now available in preview for Jira and Confluence.

Realtime allows Forge apps to subscribe and publish events to users in different browsing contexts, including the ability to publish events from Forge resolvers to the client. During Preview, Realtime can be used in production environments for your app.

Since the EAP release, we’ve implemented the following changes:

• To use global channels, you must now include the Realtime read:app-global-channel:realtime scope in your manifest. Users will then need to upgrade their installation of your app.

• The contextOverrides option now accepts Confluence context properties.

• Event payloads can now be JSON-serializable objects without needing to be stringified first. String payloads are still supported.

Run the following commands on the command line in your app directory to install the latest version of these packages and receive these changes:

• npm install @forge/bridge@latest

• npm install @forge/realtime@latest

For more information, see the Realtime documentation.

The Confluence full page module is now available in Preview. After a successful Early Access Program (EAP), we’re making the module more broadly available for developers to build fully customised app experiences within Confluence.

The EAP URL is now deprecated and will no longer work. Please update your bookmarks and use the new Preview URL format.

More details:

• Old EAP URL (deprecated):
  <https://<tenant-name>/wiki/full-page/<app-id>/<environment-id>>

• New Preview URL (Forge Apps UI Service):
  <https://<tenant-name>/forge-apps/a/<app-id>/e/<environment-id>/r/<route-prefix>/<app-route>>

For more information, see the Confluence full page (Preview)

The ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.

For more information, see App compatibility.

We’ve added new Confluence Forge events for relations:

• avi:confluence:created:relation

• avi:confluence:deleted:relation

You can use these events to invoke your Forge app function when a relationship is created or deleted in Confluence. For more details, see the Confluence events reference documentation.

You can now call Web trigger URLs with additional path suffixes. Previously, requests to a WebTrigger URL with a path suffix (for example, /hello/world) returned a HTTP 404 error. With this update, such requests are now routed to your associatedhttps://developer.atlassian.com/platform/forge/manifest-reference/modules/function/, and the suffix is available in the new userPath property of the request.

This enhancement lets you handle dynamic routes and build more flexible integrations with your Forge app.

From Apr 30, 2026, the nodejs20.x runtime will be deprecated. This is in line with the Node.js version 20.x end-of-life, scheduled for Apr 30, 2026.

You must update your apps to use the newer nodejs22.x runtime before this date. Otherwise, you will not be able to deploy changes to your app.

From Nov 1, 2025, Atlassian will migrate all Forge apps to a new app lifecycle platform. This migration introduces changes to how the platform handles apps with inactive licenses:

• Unified uninstall flow:

  • Unsubscribing and uninstalling an app will be combined into a single ‘uninstall’ action.

  • When an admin selects ‘uninstall’, the app will remain active until the end of the current subscription or trial period, plus an additional 60 days, before it is permanently deleted. No further user action is required during this period.

• Expedited uninstall:

  • Admins can choose to expedite the uninstall process. This will immediately uninstall the app and forfeit any remaining subscription period.

• Legacy “free” licensing state:

  • Apps that have already passed the end of their subscription or trial period will temporarily transition to a legacy “free” licensing state. These inactive installations will not thus be affected by the new uninstall flow until an admin initiates an uninstall action.

  • Partners are encouraged to request that customers either re-subscribe or uninstall these apps.

Read more in the community post and our support doc.

A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-117-forge-llms/96506

To maintain trust in the Runs on Atlassian (RoA) program, apps that use Atlassian API tokens (personal access tokens) to interact with first-party apps are no longer eligible for the RoA badge. Such apps will lose their RoA eligibility on Nov 3, 2025.

Apps must rely solely on oauth scopes and leverage the built-in api.asUser or api.asApp functions to call first-party app APIs.

You can now provide dynamic descriptions for the configuration of Forge workflow conditions, validators and post functions. These descriptions will appear on the overview card for configured rules in the new workflow editor and help admins locate previously configured rules.

Use the configurationDescription property and provide a Jira expression, which can reference the config context variable to describe the current configuration of the rule.