Changelog

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-51-multiple-help-centers-on-jira-service-management/79958.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-50-let-users-easily-interact-with-and-configure-macros-in-the-editor/79871.

The UI modifications (UIM) module now supports three new entry points for the issue view:

• list

• issues

• search

The complete list of supported entry points is available here.

We've updated our https://developer.atlassian.com/platform/forge/deprecation-policy/ to set clearer expectations regarding the lifecycle of Forge CLI versions. Versions older than 6 months are automatically unsupported and may have unexpected behaviours. We recommend regularly updating to the latest CLI version to benefit from new features and improvements.

You can now use the latest version of UI Kit to add configuration to Custom UI macros. Custom UI apps were previously limited to using the UI Kit 1 implementation of macro config.

For more information on adding configuration to the Confluence macros, see the Add configuration to a macro tutorial.

Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.

Run npm install @forge/react@latest on the command line to install the latest version of @forge/react.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-49-chart-components-for-ui-kit/79552.

Previously, you can download app logs dating up to 60 days from the current date. For compliance and performance reasons, we’re changing this, from 60 days to 30 days.

The Native Node Runtime is now generally available. To use this runtime, specify set your app.runtime.name to nodejs18.x in the manifest file.

As of version 9.0.0 of the @forge/cli, the app.runtime.name field of the manifest file is now required. We recommend that you use the native Node runtime, as this provides several security and performance enhancements, along with greater compatibility with the Node.js ecosystem. See More details for information on choosing a runtime.

forge tunnel for the legacy runtime will require app.runtime.name regardless of the @forge/cli version used. forge tunnel for the legacy runtime always uses the output of forge lint from the latest @forge/cli version.

Some existing apps may need to address breaking changes with the native Node runtime. Forge supports using the legacy runtime while addressing those changes. For more information, see Migrating from the legacy runtime.

We recommend that all apps use the native Node runtime, as the legacy version will eventually be deprecated.

All templates now include app.runtime.name: nodejs18.x. When creating a new app, the CLI will specify this runtime by default.

https://developer.atlassian.com/platform/forge/runtime-reference/external-fetch-api/ is now supported with the latest version of @forge/api.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-47-evolving-the-developer-canary-program-associated-developer-assistant-apps/79453.

A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-45-upcoming-changes-to-jira-navigation/79375/70.

Forge app names can now be up to 60 characters when:

• Set via the Forge CLI, or

• Updated in the Developer Console.

Previously, Forge app names were limited to 50 characters, while Marketplace listing names could be up to 60 characters in length.

Following our recent preview release of Forge UI Kit 2, we're excited to announce that UI Kit 2 is now generally available. With this release, UI Kit 2 has been promoted as the latest version of UI Kit and will now be referred to as simply UI Kit.

For more detailed information on using UI Kit components to design and build apps, please refer to our UI Kit components documentation.

The latest version is supported within the following products:

• Bitbucket

• Compass

• Confluence

• Jira

• Jira Service Management

With Forge UI Kit now generally available, we’re releasing a new major version of the Forge CLI.

Here’s a summary of the CLI changes:

• We’ve renamed UI kit 2 (Preview) template option to UI Kit.

• We’ve removed the original UI kit template option. This means no new UI Kit 1 apps can be created with this latest version.

To install the latest version, in your terminal, run: npm install -g @forge/cli@latest

We have now added the following rate limits to WebTrigger GraphQL operations:

• createWebTriggerUrl - 500 requests / 60 seconds

  • This include usage of the webTrigger.getUrl method from the @forge/api NPM package.

• deleteWebTriggerUrl - 500 requests / 60 seconds

• webTriggerUrlsByAppContext - 1000 requests / 60 seconds

Each limit is applied with the following dimensions: appId + site + forge app environment + userId.

For more information, see https://developer.atlassian.com/platform/atlassian-graphql-api/graphql/#rate-limiting.

The UI modifications (UIM) module now supports new fields on the following views:

• Parent

• Components

• Reporter

• User picker

• Multi user picker

• Parent

The complete list of supported fields for the issue view is available here.