Forge manifest scope not applied when installing app via Bitbucket Pipelines

Forge
,
1

Hi everyone,

I’m facing an issue with Forge manifest scopes that I’ve never encountered before.

I recently added a new scope to my manifest.yml:

manage:servicedesk-customer

:white_check_mark: What works

In my local DEV environment, everything behaves as expected:

  • I run forge deploy

  • Then forge install --upgrade

  • The new scope is correctly applied to the app

:cross_mark: The issue

When deploying via Bitbucket Pipelines, the behavior is different.

The pipeline performs the following steps:

  • forge deploy (with the updated manifest)

  • forge install on a site where the app is not yet installed

After the installation completes, the app does not include the newly added scope.

:thinking: What I find confusing

  • I am aware that a manifest change normally requires running forge install --upgrade

  • However, in this case, the app is installed for the first time via the pipeline

  • And the newly added scope is still missing after installation

So I’m trying to understand why a fresh install performed via Bitbucket Pipelines
does not seem to fully apply the updated manifest scopes.

This is not the first time we add a new scope to this app, but it’s the first time we encounter this behavior.

Has anyone experienced something similar or has an idea of what could cause this?

Thanks in advance!