Hey @RaimundasJuska,
As per RFC-71, there are two key components we are delivering:
- The Connect to Forge migration, which is now in Preview and opt-in for the reason you’ve noted. If an app wanted to, it could deliver the first version on Forge with Connect remotes and then remove them in a subsequent version prior to opting in for minor updates. This would mean that all existing customers would be moved to the most recent Forge version which does not include the remote.
- The Forge to Forge migration, which is in development. This will provide a similar mechanism through which the app can perform minor updates from earlier Forge versions to more recent versions, where there has not been an elevation of permission (i.e. a removal of remotes or scopes, or inherited scopes)