Licensed Automatic Updates

How entitled WordPress update delivery works.

Backend scope (v0.24.3): Stardetha One is the customer default; legacy mode requires an explicit IST_LICENSE_BACKEND=legacy override. The legacy behavior below does not describe Stardetha One. For One configuration, strict signature checks, a maximum 72-hour signed lifetime, target-language/memory grants, online character authorization, and licensed package updates, see Stardetha One Integration.

Legacy licensing backend

Instant Language Switcher v0.21.0 obtains update metadata directly from Stardetha Licensing Manager rather than EDD.

Update flow

WordPress checks for updates
        ↓
ILS sends license + instance ID + current version
        ↓
Stardetha /updates/check
        ↓
license and activation validated
        ↓
latest published release compared
        ↓
short-lived secure package URL returned
        ↓
normal WordPress Update now workflow

The temporary package URL contains a signed download token, not the customer's license key. The token identifies the authorized license, activation and release and expires after a short period configured on the licensing server.

Publishing a release

On stardetha.com, open Stardetha Licensing → Releases, upload the Instant Language Switcher ZIP, select the stable or beta channel, enter WordPress/PHP requirements and release notes, then publish it. The licensing manager validates the plugin name/version inside the ZIP, calculates SHA-256 and stores the package in the protected release directory.

Entitlement

Update metadata/downloads are available only to an active licensed installation. Existing translations continue to function if update entitlement is unavailable.