Changelog

The short options -v1 and -v2 of the forge version compare have been removed in major release v12.0.0 of the Forge CLI. Instead, you should use the existing long options --version1 and --version2.

For example:
forge version compare --version1=3 --version2=5

We have made this change to align with established CLI conventions around short options being single characters.

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

We’ve updated the minimum compatible Node.js version for the Forge CLI to 20.0.0. Developers running older versions of Node.js will need to upgrade to continue using the Forge CLI. This change ensures that all developers have access to the latest features, security updates, and performance improvements.

We’re introducing the ability for apps to publish events, allowing for enhanced interoperability between apps. This feature enables apps to subscribe to events using the existing https://developer.atlassian.com/platform/forge/manifest-reference/modules/trigger/ module, opening up new possibilities for app interactions.

Forge apps can now impersonate any user from their context. This includes impersonating other users given a user ID, and impersonating users when no user is in session, such as from a scheduled trigger or product event listener. Apps will need to declare properties on their existing scopes to be able to do this. See https://developer.atlassian.com/platform/forge/apis-reference/fetch-api-product.requestjira/ for more details on how to use this on Forge functions, and https://developer.atlassian.com/platform/forge/remote/calling-product-apis/ for more details on how to use this on Forge remotes.

We have published a new migration guide to assist you in transitioning your Forge custom fields to use the isInline property.

The guide includes two practical examples:

• Migrating a Forge custom field to render inline

• Migrating a Forge custom field to render in a modal

For more details, please refer to https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/#inline-edit-migration-guide

The list of modified fields in the Jira workflow validator has been expanded to include two new fields:

• Linked Issues

• Comment

For a complete list of all supported field types, please refer to the documentation: Jira Workflow Validator.

We've added an openOnInsert parameter for macros with classic configuration. This parameter allows you to control whether the configuration panel is automatically opened on macro insert, enhancing the user experience by providing more flexibility.

To use this feature, you must be on the latest @forge/cli version 11.6.0. For more information, see the macro module documentation.

We’ve added the ability to see insights into rate limits faced by your app into the developer console.

The new Rate limited label will be shown in the usual error metrics tab of the developer console.

We’ve added a new command, forge build, to the Forge CLI that lets you bundle and upload builds of your Forge app without deploying them to a specific environment. This command includes the subcommand forge build list to list out the builds for your app.

Builds are environment-agnostic and can deploy to any environment. Each build is assigned a unique and immutable build tag, which can then be passed to the forge deploy command to deploy the build referenced by the tag.

With forge build, you can now:

• Deploy the same build across multiple environments without needing to re-bundle and upload source code

• Rollback a deployment in an environment by re-deploying an older build.

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

In partnership with Vanta, Atlassian conducted an analysis to determine how we can make it easier for developers to meet SOC 2 requirements. Apps built on the Forge developer platform can benefit from inheriting controls to meet 30% of SOC 2 requirements.

For more information, see https://developer.atlassian.com/platform/forge/forge-and-soc2/

Blob objects can now be sent and received via the events API. This enhancement allows for more efficient data handling and transmission within the API.

Update to the latest version of @forge/bridge with npm install --save @forge/bridge@latest

We’ve added additional project information to the extension context for Forge custom fields on Jira Service Management portal requests. This allows accessing project.id directly from the extension data to avoid unnecessary REST API calls.

Making an egress fetch call to an invalid URL now throws an Invalid URL error instead of a 400 response. This updated logic is consistent with how the native Node.js fetch handles invalid URLs

We have increased the outbound request timeout for Forge apps using long-running functions from 55 seconds to 180 seconds. Outbound requests refer to fetch requests, including both product REST API and external API requests.

Forge developers can use long-running functions when processing async events, allowing functions to run for up to 15 minutes. Currently, a single outbound request will timeout after 55 seconds. This change increases the timeout of a single outbound request from 55 seconds to 180 seconds, and is now documented in https://developer.atlassian.com/platform/forge/platform-quotas-and-limits/#invocation-limits.

This prevents premature timeouts and allows Forge apps to accommodate more complex operations, such as handling large data processing tasks. This change applies to all outbound requests made from Forge functions.

We’ve added new Confluence product events for labels:

• avi:confluence:created:label

• avi:confluence:added:label

• avi:confluence:removed:label

• avi:confluence:deleted:label

You can use these events to invoke your Forge app function when label is created, added to an entity, removed from an entity, or deleted. For more details see https://developer.atlassian.com/platform/forge/events-reference/confluence/#labels.