Changelog

The route function can now accept other routes and can be used inside api.fetch(route). This enables usages like api.fetch(route${baseRoute}/specific/api).

Each app is now limited to 30 logs per invocation. Previously, this limit was 100 per invocation.

We've released Forge bridge version 2.0.0, which enables custom UI apps to request Jira and Confluence REST APIs directly from the frontend, without the need to proxy them through a custom UI resolver. This means you no longer need to define a custom UI resolver to use the requestJira and requestConfluence bridge methods.

This change also lifts the 10-second timeout previously applied when using resolvers and lets custom UI apps request endpoints that return non-JSON responses, such as attachments.

Run npm install @forge/bridge@latest in your resource directory to install the latest version.

This release includes:

• Added --non-interactive flag to forge install --upgrade command. With the --non-interactive flag, --site, --product and --environment options are required. These flags skip all upgrade prompts and allow install --upgrade to be run in CI.

• Support for optional chaining in JavaScript files. For example, writing hello?.world in a JavaScript file is now possible.

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

Both Jira custom field and Jira custom field type modules can now store data of the object type. See the object type documentation for both modules for more details.

Starting today, we’re requiring newly deployed apps to configure runtime egress permissions in their app manifest. Apps without runtime egress permissions configured will no longer work as expected.

See this deprecation notice for more details.

This release includes:

• A fix for the linter not suggesting the correct scopes when using the properties API from @forge/api.

• Improved reporting of some runtime errors as seen from forge logs.

• Various UI improvements.

• Custom UI and forge tunnel now work correctly for apps installed onto *.jira.com sites.

We've removed support for the login:ci command from the Forge CLI.

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

This release includes:

• Support for fonts and frames in custom UI external permissions.

• Support for new OAuth scopes for Confluence task events.

• Support forforge lint detecting missing permissions of content property methods (for example, properties.onJiraProject).

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

With the new props appearance and openNewTab, you can now configure the Link component to appear as a button, and to open in a new tab. See the Link documentation for more details.

Run npm install -g @forge/ui@latest in your resource directory to install the latest version of the UI kit.

We've added the authorize method, which allows app developers to authorize users and entities (for example, issues, and pages) before making asApp product REST API calls. See the Authorize API documentation for more details.

Run npm install -g @forge/api@latest in your resource directory to install the latest version of Forge API.

This release includes:

• Compatibility with projects using Typescript versions earlier than 3.8.

• The ability for developers to import and use the StorageAPI type in their code

Run npm install -g @forge/api@latest in your resource directory to install the latest version of Forge api.

This release includes:

• Enable forge deployment and installation commands for apps with more than 20 installations.

• A fix for fetch permission linter.

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

Forge storage version 1.0.4 and Forge resolver version 1.3.2 are now compatible with Node 14.

In your resource directory, run the following commands:

• npm install -g @forge/storage@latest to install the latest version of Forge storage

• npm install -g @forge/resolver@latest to install the latest version of Forge resolver

With the Update custom field configurations operation, you can now store on a custom field context the information that a Forge app uses to configure a custom field type.

A Forge app can access configuration values via Jira expressions (for example, via field data validation) or by using the Get custom field configurations operation.

See Custom field type configuration for more details.