mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-10-28 08:41:44 +00:00
* fix: use bashio::app.* instead of the deprecated bashio::addon.* bashio v0.18.0 renamed every bashio::addon.* function to bashio::app.* and keeps the old names as aliases that log "bashio::addon.X is deprecated" the first time they run, which current base images (bashio v0.19.0) now print. Rename every call across the add-ons and .templates. bashio::app.* does not exist before v0.18.0, so ha_automatic_packages.sh now installs v0.19.0 and also replaces an older bashio (no apps.sh) that a pinned base image ships; the add-ons that install bashio themselves (cleanuparr, maintainerr, netalertx) move from 0.14.3 to 0.19.0. The standalone shim defines bashio::app.* and keeps bashio::addon.* as silent aliases for user scripts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: drop add-on version bumps; pin every bashio to 0.19.0 The rename ships with each add-on's next upstream release instead of a rebuild of all of them now, so config.yaml and CHANGELOG.md are back to master. Every place that names a bashio version (ha_automatic_packages.sh, the Dockerfile pins and ENV lines, the weekly updater workflow) now names the same one, 0.19.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * chore: move pinned Home Assistant base images to releases with bashio 0.19.0 The add-ons pinned to an old hassio-addons base image carried bashio 0.14.3 to 0.17.5, which has no bashio::app.*. Move them to the latest releases, which ship bashio 0.19.0: base 21.0.10 (portainer, portainer_be, portainer_agent, zzz_archived_tor, and spotweb's Dockerfile default) and debian-base 9.5.1 (bitwarden, collabora). Add-ons on :stable and home-assistant/*-base:3.23 already get 0.19.0 and are unchanged. tor's build.json loses its armv7 entry, which the add-on no longer declares and base 21.0.10 does not publish. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>