Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Warning
titleUpgrading Multiple Versions

It is not always possible to upgrade multiple versions in one step. When this is not the case, if you attempt to skip a critical release you will see this message when trying to update the database schema:

Cannot automatically upgrade past version x.y.z. Please upgrade to that version first.

You must download and upgrade successfully to the specified version. This is the list of versions that block upgrading:

If you are currently runningYou must upgrade to this releaseBefore being able to upgrade to this release
v0.9.3 or earlierv0.9.4v1.0.0
v0.9.4v1.0.0Any later release



Info
titleReview Installation Instructions

You should review the general installation instructions to check for any changes to minimum version (eg: minimum PHP version) and other requirements. 


Backup Your Database

While upgrading is usually a fairly straightforward process, from time to time fairly significant database changes are made. Efforts are made to make these changes transparent, but as a precaution you should create a backup of your database prior to upgrading in case you need to revert the upgrade.

...

Once you upgrade to this version

You should drop these tables (if present)

Registry 0.8.2

cm_co_changelog_provisioner_exports

Registry 2.0.0cm_organizations
Registry 3.3.0

cm_co_service_tokens (but be sure to convert any tokens you wish to keep)

cm_co_service_token_settings

Registry 4.1.0cm_password_reset_tokens

Version Specific Database Updates

...