The Marketplace detects changes to the descriptor, and automatically creates a new version of the add-on. Installations of Jira Cloud then upgrade themselves to use the new add-on version over the next ten hours or so. Cool.
When a Jira Cloud instance upgrades itself, is it the case that both the
/installed, and the
/enabled life-cycle webhook calls are made to the add-on?
Our add-on needs to differentiate between host applications using the old descriptor, and those that have upgraded to the new descriptor. If the new descriptor includes a URL like this:
…then maybe that’s a way for the add-on to learn that a particular Jira instance has upgraded to version 2.0.
Can you give me a sanity check on this before I spend time implementing it?