Swapping Scopes in Forge triggers major version update?

Forge
, ,
1

Hi all,

We’re about to upgrade a Forge App from Confluence Version 1 REST API to the Version 2 REST API.

  • The V1 Api needs this scope to read tasks: read:inlinetask:confluence
  • The V2 Api needs this scope to read tasks: read:task:confluence

Does this scope change trigger a manual major version upgrade for end users?

2

Seems like this is how it currently works.

Same applies if you switch from the Confluence Space V1 Rest API to V2 Rest API: the V2 API for listing spaces requires the read:space:confluence scope, whereas the V1 API used read:confluence-space.summary

Really bad design of the versioning of Forge apps.