Upgrade with Composer

This assumes that you are already using Opigno 2.x (this does not cover upgrading from Opigno 1.x branch).

This also assumes that you initially installed Opigno using Composer. If you initially installed Opigno by downloading the tarball version, upgrade with Composer won't work.

If there are updates for Opigno LMS you can easily install them with Composer.

All Composer commands must be executed in the folder of your project at the same level as the folders web, drush etc.

First, you need to check if updates are available:
composer outdated opigno/opigno_lms
If 'version' and 'latest' are different that means updates are available.
Install updates:

- UPDATING TO 8.x-2.12 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.13 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.14 version: get this   file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.15 version: get this   file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.16 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.17 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.18 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.19 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.20 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.21 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.22 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.23 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.24 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.25 version: get this file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.26 version: get this   file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.26.1 version: get this   file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.27 version: get this  file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.28 version: get this  file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.28.1 version: get this  file. Then replace your old composer.json with a new one and then run the commands below
- UPDATING TO 8.x-2.29 version: get this  file. Then replace your old composer.json with a new one and then run the commands below
// Clear composer cache composer clearcache // Check if updates will run without any issues composer update --dry-run // Run updates composer update

During the update process some warnings may appear in relation with some modules (drupal/calendar, drupal/views_role_based_global_text), mentioning that they were modified, and asking "Discard changes?". The answer should be "y".
These modules will be updated to new versions.

Then update database and clear cache in admin interface or by Drush:
drush updatedb drush cr

Typical problems:

If updates are available but can't be installed you can run this command to check the reasons why it can't be done:
composer prohibits opigno/opigno_lms