The automatic system update debuts

Until August 2025, updating an installation meant replacing files by hand. That month the automatic update system debuted: the installation fetches the release package, checks it and applies it.

What landed

• Core update from the package published in the release.
• Package verification by checksum.
• Version management and update validation.

Two days later, the update system was consolidated and documented.

Why it matters

It is the first step of a line that runs to this day: next came the update through the API, the deploy lock, the snapshot, the health check and the automatic rollback. They all start from the idea of this delivery: updating has to be an operation of the system, not a manual procedure.