Upgrades are Permanent
If you want to upgrade to a newer version available in the catalog, you must install that upgrade yourself. An upgrade is a “change” that must be added to a library, tested, and published before it impacts your deployed tags.
Upgrading should not be taken lightly. You should not upgrade unless you are prepared to test the new extension and are ready to deploy it. Once the upgrade has been added to your property, it must be included in all libraries. Any library that does not include the upgraded extension will fail at build time.
There is currently no capability to downgrade your extension to a previous version. Once you’ve upgraded (whether you publish or not), the new extension version is on your property to stay.
Upgrade Process
Installing an upgrade is pretty much the same as installing the extension for the first time.
- Select Upgrade to go to the Extension Configuration screen.
- Make any configuration changes you’d like to make.
- Select Save.
The upgrade is not actually performed until you hit Save. At any time previous to that, you can select Cancel and stay with the currently installed version. Selecting Save is the point of no return.
Extension Upgrades are not permitted if you have a library in the Approved
or Submitted
state. This is because the next build must contain the new extension version. For a library that is Approved
or Submitted
, the next build is the production build. That build would fail since it doesn’t contain the latest version, so the workflow is to publish or reject libraries in the Approved
or Submitted
state before upgrading the extension.