Which update scheme to choose for the site?

Question

CMS

In the system, you can select the kernel and modules, periodically the kernel and modules are updated, and each module works with its own version of the kernel. I see the following upgrade options:
1. There is a common CMS on the server, projects use one core and system modules in terms of code Individual settings, templates and modules are placed in the project directories. Periodically, a kernel version is added and projects that are subscribed to updates simply switch to the new version.
2. There is a section in the admin part that displays information that a new version of the kernel and modules has appeared, respectively, the update occurs through the admin interface.
I would like to hear if there are other options? So are the pros and cons.

Answer 1

use the composer , Luke.
You can configure each project for different versions of packages, you can check for updates, in short, resolving dependencies and their versions can be completely left to composer.

Answer 2

github + gitignore