Updating Evolution Through the Extras-Evolution Repository

One of the recurring questions from the old Evolution ecosystem was whether the CMS itself could be updated through the Extras-Evolution repository in the same way as add-ons.

Why the Idea Was Attractive

A repository-driven workflow promised a simpler maintenance path: install, update, and manage packages from one familiar place instead of moving files manually every time.

Why Teams Still Had to Be Careful

• core updates can affect database behavior, manager code, and templates at once
• extras compatibility still has to be checked separately
• repository convenience does not replace backups and staging
• custom builds may diverge from official releases

Practical Rule

Even when a repository can deliver the package, treat a core upgrade as a release operation, not a casual click. Backup first, check compatibility, and review what exactly is being installed.

This topic belongs in the ecosystem history because it reflects how Evolution gradually moved toward more centralized package distribution without removing the need for disciplined deployment.

Source: original community announcement. Related context: repository background and goals.