1.5.0

Added

• Forced vs optional updates. Versions and bundles now carry an update_type (optional, the
  default, or force), set per row in the dashboard. The OTA update check reports it on each offer as
  availableUpdates.version.updateType / availableUpdates.bundle.updateType, so the client can force
  the user to install instead of offering a "Not now". Backward compatible: older clients ignore the
  field, and a client talking to an older server treats the update as optional.
  • New migrations add the column to versions and bundles; both models expose it in toArray() and
    accept it in their validation rules (the rules are the write whitelist). Adds OtaUpdateTypeTest.