DrelVersions and change policy
Read versions from window.DrelRuntime at runtime and feature-detect individual fields. Never assume that a future Drel release grants a remote page new native powers.
Current public contract
| Surface | Version | Meaning |
|---|---|---|
| Drel app | 1.4.x | Push, HTTPS container, registered web apps and offline-package v1. |
| Container protocol | containerVersion: 1 | Versioned UA token and DrelRuntime environment object. |
| Offline package protocol | offlinePackageVersion: 1 | Hash-verified, atomically activated package support. |
| Native Bridge | bridgeVersion: 0 | No remote-page native Bridge is available in the Store container. |
Compatibility rules
- Minor app updates can add optional fields. Integrations must ignore unknown fields and tolerate missing optional fields.
- A documented stable field is not silently redefined. If a breaking change is necessary, it receives a new versioned contract or a deprecation period.
- Undocumented endpoints, aliases and experimental fields have no compatibility promise.
- The app version is not an authorization level. A page must still feature-detect, validate its own data and use ordinary web fallbacks.
Self-hosting status
Self-hosting documentation is separate because a stock Drel install and a deployment with an authorized APNs signer have different responsibilities. Read Self-host Drel Push before deploying. Never paste a private APNs signing key into a webpage, repository, chat, device QR code or public configuration.