Forge linter false positive: egress-permission-required for @forge/bridge requestJira/requestConfluence

Forge Forge Platform and Tools
1

Description:
The Forge CLI linter reports egress-permission-required errors for “jira” and “confluence” domains in my frontend bundle, even though my code only uses @forge/bridge’s requestJira and does not make any direct fetches or hardcoded requests to those domains.

Steps to Reproduce:

  1. Use @forge/bridge’s requestJira in a Custom UI app.

  2. Build the frontend bundle (e.g., with esbuild).

  3. Run forge lint or forge deploy.

  4. Observe linter errors for “jira” and “confluence” domains.

Expected Result:
No linter errors, since @forge/bridge is the recommended and supported way to call Jira/Confluence APIs from Custom UI.

Actual Result:
Linter fails with:

  • error The domain confluence is not included in the “permissions.external.fetch” section of your app’s manifest.yml file egress-permission-required

  • error The domain jira is not included in the “permissions.external.fetch” section of your app’s manifest.yml file egress-permission-required

Workaround:
forge deploy --no-verify works, but this is not ideal for CI/CD.

Additional Info:

  • Only @forge/bridge is used for Jira/Confluence API calls.

  • No direct fetches or hardcoded URLs in my code.

  • Linter is flagging internal code from the @forge/bridge package.

Using forge cli 12.16.0