Hi everyone,
Thanks for raising this. We understand the frustration and the impact of this change on your apps and your business.
To be clear, we are treating this as a bug, not the intended end state. This may not have come across clearly in the changelog. We are actively working on restoring storage:app as a scope change that can be managed through bulk upgrade, removing the need for individual site admin approval. We will provide an update on this thread and this bug ticket with fix timelines as soon as we can.
Looking further ahead, we’re building Rolling Releases, which will fundamentally change how Forge versioning works. With Rolling Releases, code updates are decoupled from permission changes. This means your latest code ships to all installations without admins pressing update, while new permissions are handled gracefully at runtime using our Permissions SDK. This eliminates the “zombie app” problem where installs get stuck on outdated versions. Once Rolling Releases is fully live, the manual bulk upgrade command will no longer be needed. When you deploy, upgrades roll out automatically as part of the release. Rolling Releases is currently in EAP, and storage:app transitions are not yet supported. Bringing storage:app into scope is a priority for the next milestone, so that adding storage to your app will no longer create version fragmentation at all.
Thank you.