Changelog

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.

You can now enable your Forge workflow conditions, validators and post functions in team-managed workflows. Use the projectTypes property to configure whether your rule should be enabled for company-managed projects, team-managed projects, or both.

AppDataListResponse in the Forge migration API has been updated to match the actual response.

Previously, the definition didn't match the API response, which could cause cast errors or undefined object errors when accessing response fields. This fix ensures the response structure is consistent with the API documentation, so the API can be effectively used to migrate apps from Server or Data Center to Cloud.

If you were using the previous definition, you may see a compile error after updating. To resolve this, change any usage of response.result to response when calling this API.

The following UI Kit Editor components are now available through Forge’s Early Access Program (EAP). To join, please complete this sign-up form.

• Chromeless editor

• Comment editor

These components are available in Confluence and Jira modules.

A new RFC is ready for review at : https://community.developer.atlassian.com/t/rfc-116-new-link-egress-type-for-forge-apps/96445

Following two RFCs related to Dynamic Modules on Forge

https://community.developer.atlassian.com/t/rfc-95-forge-dynamic-modules/92696

https://community.developer.atlassian.com/t/rfc-98-follow-up-forge-dynamic-modules/93532

we are now announcing the start of the dynamic module EAP on the 17th November.

The scope of this EAP will be triggers. More Jira modules will subsequently be released for testing.

As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” (set forth in section 10 of the Atlassian Developer Terms) and are unsupported, subject to change without notice, and are not recommended for use in production environments.

To participate, please sign up for the EAP here.

The Forge Model Context Protocol (MCP) Server is now in preview. This new remote service enables Forge app developers to use coding agents with up-to-date Atlassian Forge and Cloud documentation, including markdown-based guides, module catalogs, and manifest references. The Forge MCP Server also offers a search feature for Forge reference documentation and implementation patterns. These features are designed to streamline Forge app development in AI-powered workflows. We invite you to try the Forge MCP Server (preview) and share your feedback to help us improve.

When defining resolvers, the front-end code can share the types with the backend so the invocation interface is type-safe. This helps catch potential errors during compilation.

The following Confluence display conditions are now generally available:

• entityPropertyContainsAnyUserGroup

• hasPagePermission

• hasSpacePermission

• userIsExternalCollaborator

• Confluence Entity Property conditions now also support app and user properties

Learn more about these conditions here.

We've enhanced the Forge Bitbucket event for pull request reviewer status updated. The event payload now includes a new reviewers field, which provides the latest status of each reviewer on the pull request.

This addition makes it easier to track reviewer decisions and automate workflows based on reviewer status.

For more information and example payloads, see the Bitbucket Forge events.

Starting in Forge CLI version 12.6.1, you can now control the title, icon, and tooltip properties of the confluence:contentBylineItem module dynamically using content properties.
Specify a contentPropertyKey in your manifest.yml to enable Confluence to retrieve these properties from the corresponding content property value when your app initially renders.

You can now programmatically refresh the byline module properties using either:

• The https://developer.atlassian.com/platform/forge/ui-kit/hooks/use-content-propertyuseContentProperty hook (available in @forge/react version 11.4.0 and above), or

• The https://developer.atlassian.com/platform/forge/apis-reference/confluence-api-bridge/updateBylinePropertiesupdateBylineProperties method (available in @forge/confluence-bridge version 3.1.0 and above).