Hello there !
We are developing a Forge application which is installed via an installation link since it is multi-product (Jira + Confluence).
When deploying the Forge Application to the Production environment, the application gets updated automatically in all the Atlassian sites where it is installed.
Some clients would want the update immediately, some want to have control over when the update is performed.
We want to be able to control the update of the Forge Application. We want the application not to be updated automatically but providing a manual update button.
Is there a proper way of complying with this requirement ?
Thanks !
Hi @FabienLydoire. TL;DR - for minor version updates (the ones that automatically roll out to instances), you cannot set an instance to be manual upgrade only. Manual upgrades (requiring consent from admin) only apply to major version updates.
You probably know the following information, but I’ll share for other folks who might not. See the page on App versions and upgrades: https://developer.atlassian.com/platform/forge/versions/
Major version upgrade: when you make significant changes that require re-consent from user/admin, the updates are not rolled out immediately. What kind of changes constitute a major upgrade? Significant changes to manifest such as: modifying scopes, content permissions, external permissions, providers, etc. More details here.
Minor version upgrade: Changes that do not require re-consent from admin. For example, making changes in your app’s source code (fixing a bug, adding a feature), are considered minor upgrades as long as they do not require any additional changes be made to manifest (like mentioned above).
3 Likes
Thanks for the pointers to the doc @nmansilla !
I indeed was aware of those mechanisms.
Is there a way to manually trigger a Major version upgrade without having the Forge packaging system deciding for me ?
I would like to be able to have a bit of control over the versioning of my own Forge app.
Let’s say I introduced a new breaking change (like changing the way data is stored) and I want to mark my new version as Major, but none of the changes are the ones listed here.
Would it be possible to manually bump the major version ? Maybe something with the @forge/cli like
forge version major bump
It would force a major version bump and consequently enforce a Manual upgrade.
On the other hand, I could fulfill my Manual Update requirement if there were a Site setting allowing admins to opt-out from the automatic update. Do you know if there is such a setting ?
3 Likes