Automatic Atlassian Connect add-on polling & versioning

We automatically detect updates to Atlassian Connect add-ons with a polling service. We poll the add-on descriptor URL that you included when you submitted your listing every minute. When we detect a change, we automatically update your add-on in the Atlassian Marketplace with a new version. The way we increment your version number depends on the changes made to your descriptor. 

We poll and update your add-on so that you can easily release fixes and new features, without having to manually create new version entries on Marketplace. We want to ensure that customers get the latest version of your add-on with as little delay as possible – Connect add-ons should seem like web services, not versioned software. 

Major, minor, and micro version update definitions

Updates are published to the Marketplace within a few minutes of detecting changes from your Atlassian Connect descriptor. Customers automatically receive updates via the UPM within 6 hours. Any change to your service that does not alter your add-on descriptor will be immediately available to users and will not result in a new version on Marketplace.

We automatically increment the version for your add-on as follows:

  • The major version is incremented (e.g. from 1.2.3 to 2.0.0) when you specify an API version update (e.g. from 1.0 to 2.0). The new major version matches the API version listed in your descriptor.
  • The minor version is incremented (e.g. from 1.2.3 to 1.3.0) when you specify increase/changed scopes, and/or when you update licensing from free to paid. Customers must manually approve updates for minor version updates.
  • The micro version is incremented (e.g. from 1.2.3 to 1.2.4) when you make any other descriptor changes not included above that do not require manual approval.

Changes that require manual customer approval

Even though your add-on is automatically updated in the Marketplace, certain scenarios require customers to manually approve your add-on'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 add-on.

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 add-on, 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 add-on.

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.

Viewing automatically added versions

You can view add-ons in the Marketplace the same way you manage other add-on versions: 

  1. Log in with your vendor credentials.
  2. Click Manage vendor account from the profile menu (upper right).
  3. Click your add-on's name from the list.
  4. Click Versions in the horizontal navigation bar.
  5. You'll see updates from Marketplace Hub [Atlassian]:

Was this page helpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport