Files
hassio-addons/portainer_be/CHANGELOG.md
Alexandre 74121509cd fix: give every addon a version Home Assistant can order (#2926)
Seventeen addons carried a config.yaml version that awesomeversion, the
library Home Assistant orders versions with, reports as UNKNOWN: text
tags such as version-bf9e0b4f or sts, LinuxServer tags such as
v26.2-ls256, and local counters written as a semver pre-release such as
15.7-47. Home Assistant cannot tell which of two such versions is newer,
so update detection depends on a compare exception rather than on
ordering, and any version that becomes partially comparable silently
stops being offered.

Each version keeps every number it carried, as a section of its own:
v26.2-ls256 becomes v26.2.256, 4.16-r0-ls95-7 becomes 4.16.0.95.7 and
5.0.0b5-3 becomes 5.0.0.5.3, so nothing that ordered the addon is lost
and no previously published version is reused. The two versions holding
no number at all use the date instead. Only config.yaml and CHANGELOG.md
change, so every addon still builds from the upstream tag recorded in
its Dockerfile and updater.json.

Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
2026-08-01 18:51:31 +02:00

703 B

2026.08.01 (2026-08-01)

  • Version renamed from sts, which Home Assistant could not order and therefore could not reliably offer as an update: the previous version held no number that could order it, so the date of this change is used. The addon itself and the upstream version it tracks are unchanged

sts (2026-08-01)

  • Update to latest version from portainer/portainer-ee

2.43.0 (2026-07-27)

  • Initial release: Portainer Business Edition add-on, based on the Portainer (CE) add-on (#873)
  • Ships the portainer/portainer-ee binary and web assets; enter a free Business Edition license key in the web UI to unlock BE features (changelog: https://github.com/portainer/portainer/releases)