Upgrading Corteza

This guide helps you upgrade your Corteza to the newest version in no time!

While there are internal safeguards in place that can prevent data loss or other kinds of disasters, make sure you backup your database before you upgrade. Refer to devops guide on backup procedure for details.

If you are upgrading multiple versions at the same time; for example from 2019.12 to 2020.9; you should follow all the upgrade guides between the two versions.

Recommended Steps for Corteza Upgrade

Especially before any major version upgrade, it is recommended that before upgrading your production you either:

  • upgrade your staging environment, or

  • deploy a temporary environment with a copy of the production database and perform a test upgrade there.

Steps to upgrade Corteza when deployed with docker-compose:

  1. changing image versions in your docker-compose.yaml (or .env) file,

  2. pull new images from docker hub with docker-compose pull,

  3. recreate containers with docker-compose up -d.

Upgrading to 2023.3

After the Upgrade

Corteza 2023.3 introduces a new resource - corteza:compose:page-layout. As with most other resources, it introduces new RBAC rules.

Re-visit your security model setup and adjust your RBAC rules to incorporate the new resource.

If a specific role does not have read access to a specific page layout, that layout will not be shown and some pages may appear empty (due to no page layouts being available).