We’ve released version 4.5.0 of the Forge CLI. This update includes:
We’ve updated the Forge CLI to align the experience of upgrading and uninstalling JSM apps for classic or granular scopes.
Now, for JSM Forge apps, the Forge CLI does not show JSM as an option when you upgrade and uninstall the app. When the apps are installed, upgraded, or uninstalled in Jira the changes are reflected in JSM.
For more information on classic or granular scopes, see the Jira or JSM Scopes for OAuth 2.0 (3LO) and Forge apps pages.
We’ve introduced the jira:workflowCondition Forge module.
You can now configure your own workflow conditions using Jira expressions.
See the Jira workflow condition documentation for more details.
Additionally, we’ve introduced a new avi:jira:failed:expression Jira event you can subscribe to using a trigger module. This event is generated whenever an app-registered Forge workflow validator or Forge workflow condition based on a Jira expression fails while executing.
See the Jira expressions events documentation for more details.
Forge CLI now lints correct scope when Jira Software and Jira Service Management REST APIs are used.
The scope checks are based on the OpenAPI specifications:
- Jira Service Management: https://developer.atlassian.com/cloud/jira/service-desk/swagger.v3.json
- Jira Software: https://developer.atlassian.com/cloud/jira/software/swagger.v3.json
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.