avm/hassio-addons
1
0
Fork 0
mirror of https://github.com/alexbelgium/hassio-addons.git synced 2026-10-10 18:21:36 +02:00
Code Issues Packages Projects Releases Wiki Activity
Files
revert-3069-master
hassio-addons/browser_chromium/CHANGELOG.md
Alexandre ced15122d9 Migrate legacy addon_config maps to app_config (#2937) nobuild 
* 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>
2026-09-11 09:30:49 +02:00

3.4 KiB
Raw Permalink Blame History

  • Migrate legacy add-on configuration map names to current app configuration terminology.

2026.09.05 (2026-09-05)

2026.08.13 (2026-08-13)

2026.08.01.1 (2026-08-01)

2026.08.01 (2026-08-01)

  • Version renamed from version-bf9e0b4f, 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

version-bf9e0b4f (2026-07-25)

version-ae9a7fca (2026-07-16)

version-30a7c401 (2026-07-11)

version-7148c2a3 (2026-07-04)

version-ec868334 (2026-06-27)

version-b9b82d3e (2026-06-20)

version-cca5154d (2026-06-11)

version-89f88890 (2026-06-05)

version-b0ddd401 (2026-05-30)

version-1e736296 (2026-05-22)

version-09ce6dc3 (2026-05-16)

version-3f0abc3c (2026-05-09)

version-5dea07d5 (2026-05-02)

version-91d1c203 (2026-04-23)

version-858340b9 (2026-04-18)

version-76e3a185 (10-04-2026)

  • Minor bugs fixed