Devani updates are opt-in. Your site checks the published release feed and tells you when a new version exists — but nothing installs until you choose to.
How it works
- Devani publishes each release at
https://devani.io/latest.xml— version, download URL, and a SHA-256 checksum. - Your admin dashboard notices a newer version and shows an update notice. This is notification only — seeing the notice changes nothing on your site.
- When you're ready, go to the System Update page in the admin and apply it. The download is verified against the published checksum before anything is touched.
Why opt-in
Auto-updates are how other CMSes break sites at 3am. Devani's position: you should update on your schedule, after reading what changed. There's no auto-update pressure and no dependency chain that forces your hand — you can even pin to a specific version indefinitely if that's right for you.
Good practice
- Read the release notes first. Security releases are labeled as such — apply those promptly.
- You're already backed up. Scheduled content snapshots and per-edit snapshots exist independently of updates, so your content is recoverable regardless.
- Updates don't touch your content. A release replaces application files; your pages, posts, products, media records, and settings live separately and carry straight through.
Checking your current version
The System Update page shows your installed version and the latest available one, side by side.