Change to the
atlassian-connect.json are typically detected automatically and pushed to all instances (see https://developer.atlassian.com/platform/marketplace/upgrading-and-versioning-cloud-apps/). However, there is a small subset of changes that require manual reinstall by system administrators.
I think this is the part which is most important:
If the changes do not require manual customer approval, they are automatically deployed to all customer instances within 10 hours:
Changes that require manual customer approval
Even though your app is automatically updated in the Marketplace, certain scenarios require customers to manually approve your app’s update in the UPM. These changes correspond to minor version updates in the table above. In these cases, we automatically send emails to the product administrator so they can approve and update the app.
These scenarios require manual customer approval:
- Your listing changes from free to paid : Your change triggers a Marketplace approval. Existing customers need to approve the change to start paying for your app, otherwise they will need to uninstall it.
- Your listing involves additional scopes: Marketplace updates happen automatically (no approval necessary), but customers need to approve the changes to continue using your app.
Before the approval, those customers continue to use the older version of your descriptor. If you can plan ahead, it’s a good idea to isolate those changes from any other changes in functionality.