In my experience the scope permission tags have been renamed and changed many times with each new @forge/* and CLI version.
ie forge lint will pass fine, some weeks/months pass and you update the CLI or a forge package, and the linter will throw errors asking you to use different scope names. You comply and thus your users are required to manually update the app yet again (which they don’t do).
Additionally there is no ability for Forge apps to fetch their own version data: No API available to get app version for Forge Apps?
So you can’t programmatically show a message such as “update to the latest version to continue using this app”.
Which then means Forge error logging becomes useless since it will simply spam your inbox with noise of bugs fixed in outdated versions that users haven’t yet updated.
I’d be happy with either:
- an API endpoint to determine latest and installed versions
- a manifest flag to auto-require admins update to the latest version to use the app
- a manual one-off trigger in the developer console to require admins update to the latest version
The entire point of cloud-based software is to have all users on the latest version so you can rapidly iterate with multiple daily deployments.