Updates

The theme keeps itself current: new releases appear in Dashboard → Updates like any other theme, with no account, token or license key. This page explains what actually happens.

How a check works

  • The theme fetches a small manifest from wprelieve.com — version, download URL, and a SHA-256 checksum. The request carries no information about your site beyond the request itself.
  • The result is cached for six hours, so admin pages never wait on the network.
  • If the manifest offers something newer, WordPress shows the normal update notice.

Every download is verified

Before WordPress unpacks anything, the downloaded zip is hashed and compared to the checksum published in the manifest. A mismatch — a tampered file, a truncated download — is refused with a plain error instead of being installed. WordPress core does this for its own updates; this theme does it for itself.

Running an old version?

Versions before 1.1.2 cannot update themselves. Upload the current zip once over the old install; from then on updates arrive on their own. The changelog lists what you have been missing.

For forks and developers

The updater is yours to repoint. A fork can serve its own manifest and set one constant:

define( 'WPR_THEME_UPDATE_MANIFEST', 'https://example.com/updates/theme.json' );

The full server-side runbook — manifest format, checksums, publishing — ships in the theme as UPDATING.md. To see exactly what the updater sees on any site:

wp wpr-update check --force