Black Friday
Skip to documentation content

Developer Reference

Separate package metadata from compatibility evidence

A version/header, a compatibility declaration, a matching archive and a successful runtime test answer different questions. A release should identify all four instead of treating a declared tested range as new regression evidence.

A version/header, a compatibility declaration, a matching archive and a successful runtime test answer different questions. A release should identify all four instead of treating a declared tested range as new regression evidence.

Identify the exact component

Free uses folder kimorapro-hotel-booking and Pro uses hotel-booking-pro; template packages can still use hotel-booking and hotel-booking-pro. Aurelia’s installable root/stylesheet and commercial product are aurelia-theme, while presentation declarations can use an Aurelia owner identifier. These strings are not interchangeable.

Record version, source commit, clean/dirty state, ZIP SHA-256/root and selected runtime identity. Current source review pins Free 3.28.0, Pro 1.36.0 and Aurelia 1.3.7. That is not an announcement that a new three-component release set was published.

Read declarations narrowly

Aurelia declares a general Core minimum of 3.19.3 and Theme Contract minimum 1.6.0. Its 1.3.7 sample-hotel wizard separately requires Free 3.28.1; the reviewed Free baseline is 3.28.0. Do not turn a general requirement into a demo-import PASS for this pair.

Legacy compatibility licensing fields also predate Aurelia’s current shared runtime gate. Use the current client/README implementation and owner review rather than inferring license-free paid presentation or token-only storage from those fields.

Preserve download integrity

Use supported updater authorization, expected version/origin, size, SHA-256 and package-root checks. A repair only in the target ZIP cannot fix the downloader already installed; inspect that installed version before assuming native update delivery works.

Do not overwrite an already published immutable version, bypass digest/TLS checks or use an arbitrary public URL for a premium package. Theme rollback, plugin schema recovery and privacy/provider reconciliation remain separate procedures.

See the compatibility matrix for source/package/runtime/publication distinctions and Aurelia updates.

Was this article helpful?

Your feedback helps us improve the documentation.