When an integration developer makes improvements to an existing integration, they release a new integration version. However, modules that use the integration continue to use configurations of the old version. Meanwhile new modules and integration configurations may still refer to old versions of the integration. Modules can only use the new integration version after an admin has created a configuration for the new version or through an automatic upgrade.
The purpose of automatic upgrades is to automatically use new integration versions when possible. In general, automatic upgrades are only possible when the new version is compatible, so that an existing configuration can be used, and existing modules’ configured actions also work. In practice, automatic upgrades will apply in specific scenarios.
Automatic upgrades reduce maintenance effort for authors and admins, who must otherwise manually upgrade modules and integration configurations, respectively. In addition to reducing effort, automating upgrades ensures that these upgrades are more likely to happen.
The integrations platform automatically publishes new versions of integrations, so that your admin can install them on your tenant and add configurations.
The integrations platform performs the following upgrades and clean-up for admins.
Automatic upgrades apply to minor and patch releases, as described by Semantic Versioning, but not major releases. For example:
Major releases cannot be upgraded automatically because they include breaking changes: the updated integration is not compatible with the existing action or integration configuration.
The integrations platform cannot currently perform the following upgrades.