Updates
Signed release packages, the automatic backup and the rollback path.
How a release is delivered
An update is a zip with a manifest and a detached Ed25519 signature. The manifest lists every file with its SHA-256, the version it applies to, the migrations to run and the minimum PHP version.
Two things follow from that:
- A package that was tampered with, or built for another version, is rejected before a single file is copied.
- A package applies only to the
from_versionin its manifest. There is no guessing and no half-upgrade.
Applying an update from the admin panel
Open Admin → Updates.
- Check now asks the release channel for the newest version available to your license. The card shows the version, build, size and notes.
- Download & install fetches the signed package, verifies it, takes a backup and applies it.
The pipeline is deliberately boring:
verify signature → verify checksums → back up files → dump database
→ copy files → run migrations → clear caches → GET /up → done
If any step fails, files are restored from the backup, new files are removed, the database is imported back and the run is marked as failed in the history with the error. The site returns to the state it had before the click.
Manual upload
Upload package accepts the same zip by hand — useful when the server has no outbound access, or when you downloaded the package from the client area.
The pipeline is identical, including the backup and the rollback.
The history
Every attempt is recorded in update_runs and shown on the same page: from, to, source (channel or manual), status, duration and the error message if there was one.
After the update
Caches are cleared by the updater. If you run an opcode cache or a CDN, purge it yourself — the site cannot know about it.
Old hashed asset files are not deleted on purpose: an open tab referencing the previous build keeps working. They are harmless and can be removed by hand.
When an update cannot be applied
| Message | Meaning |
|---|---|
Signature is invalid |
The package was modified, or it was signed with another key. |
This package updates X, the installation is Y |
Wrong from_version. Download the package built for your version. |
PHP X is required |
The server is older than the release expects. Upgrade PHP first. |
Healthcheck failed |
The site did not answer /up after the update; it was rolled back automatically. |
Downgrading
There is no downgrade button: the release channel only moves forward. To go back, restore the backup the updater took — it is listed in Admin → Backups — or unpack the previous release zip and point the database at the pre-update dump.
Requirements
Check and install are gated by the license: with an expired updates window the buttons are locked and the card explains why. The installed version keeps working regardless.
Not covered here?
Write to sales@scenecms.com — we answer within one business day.