mirror of
https://github.com/alexbelgium/hassio-addons.git
synced 2026-10-30 17:41:44 +00:00
* Add one-shot app_config linter migration workflow * Add app_config linter compatibility action * Add add-on map compatibility normalizer * Test add-on map compatibility normalizer * Run app_config compatibility preparation on pull request * Validate app_config short and long map forms separately * Export validated workflow updates * Use app_config-compatible linter for PR checks * Use app_config-compatible linter for builds * Remove temporary linter preparation workflow * Add one-shot app_config manifest migration * Migrate legacy addon_config maps to app_config * Preserve upstream legacy aliases without deprecated literals * Test legacy alias compatibility without deprecated literals * Validate completed app_config migration * Count only add-on manifests during migration validation * Remove temporary migration validation workflow * Document legacy alias construction * Remove obsolete local linter compatibility script * Remove obsolete local linter compatibility tests * fix(pr-2937-review): address reviewer findings on app_config migration - Remove the orphaned .github/actions/addon-linter composite action: it references .github/scripts/prepare_addon_lint_config.py, which was never added (the normalization approach was superseded by pinning frenck/action-addon-linter directly in #2936). Confirmed unused - no workflow invokes it. - cleanuparr: HA_DATA_DIR pointed at /app_configs/cleanuparr, a path not mounted inside the container. cleanuparr's map is app_config:rw, which Supervisor mounts at /config, so data was living on the ephemeral container filesystem. Point it at /config instead (pre-existing bug, not introduced by this PR - just carried the wrong path forward). - joplin/README.md: joplin's config.yaml still declares config:rw, not app_config (it was never part of the 86-manifest migration). Revert the doc text that incorrectly started calling it the app_config mapping. - qbittorrent/00-folders.sh: fix a pre-existing copy/paste bug in the migration marker/log for the main-folder migration block - it referenced "openvpn" and a "qBitorrent" typo instead of qBittorrent. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
32 lines
1.4 KiB
Markdown
32 lines
1.4 KiB
Markdown
- Migrate legacy add-on configuration map names to current app configuration terminology.
|
|
## v2.7 (2026-08-01)
|
|
|
|
- Version renamed from `v2-7`, which Home Assistant could not order and therefore could not reliably offer as an update: every number of the previous version is kept, as a section of its own. The addon itself and the upstream version it tracks are unchanged
|
|
|
|
## v2-7 (13-01-2026)
|
|
- Minor bugs fixed
|
|
## v2-6 (13-01-2026)
|
|
- Minor bugs fixed
|
|
## v2-5 (13-01-2026)
|
|
- Minor bugs fixed
|
|
## v2-4 (11-01-2026)
|
|
- Minor bugs fixed
|
|
## v2-3 (11-01-2026)
|
|
- Minor bugs fixed
|
|
## v2-2 (18-03-2026)
|
|
- Ensure folder permissions use configured PUID/PGID values
|
|
|
|
## v2 (11-01-2026)
|
|
- Minor bugs fixed
|
|
|
|
## 1.601 (2025-12-27)
|
|
- Update to latest version from causefx/organizr (changelog : https://github.com/causefx/organizr/releases)
|
|
- The Home Assistant project has deprecated support for the armv7, armhf and i386 architectures. Support wil be fully dropped in the upcoming Home Assistant 2025.12 release
|
|
|
|
- Added support for configuring extra environment variables via the `env_vars` add-on option alongside config.yaml. See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
|
|
|
|
- WARNING : update to supervisor 2022.11 before installing
|
|
- Add codenotary sign
|
|
- New standardized logic for Dockerfile build and packages installation
|
|
- Initial build
|