CPalius CMF 2.2.45

Released: 2026-10-12 · Channel: stable · Critical: no

Signed releases#

• Release information (latest.json) is now signed with Ed25519 and checked against a public key built into the core. An unsigned, forged, expired or older manifest is refused: the Updates screen shows "Cryptographic signature could not be verified" and the update button is disabled. Nothing is downloaded.
• The manifest carries expires_at (30 days) and min_allowed_version, which protect against replayed stale or older releases.

Safer updates#

• An update now switches the site to a 503 maintenance page, takes a lock so two updates cannot overlap, and writes files in two steps: every file is staged next to its target, then all are renamed into place in one quick loop.
• Before the update runs, a database snapshot is taken. If a file, migration or update step fails, the files and the database are restored together and the Updates screen says so.
• If the update process dies half way, the next request restores the previous files by itself (done in public/index.php, before the framework loads) and finishes the database restore on the first booted request. An update parked for more than 15 minutes between its two steps is rolled back.
• While an update is running, visitors and the panel get a short 503 page.

Database#

No schema changes. The snapshot is kept as cp-core/var/update/db-last.sql.gz. Clear cp-core/var/cache/prod/ after updating, and the Redis cache if you use one.