GitHub bot: changelog [nobuild]

Update config.yaml
2026-09-18 07:39:08 +02:00 · 2026-09-11 09:46:01 +00:00 · 2026-09-11 11:37:14 +02:00 · 2026-09-11 08:53:41 +00:00 · 2026-09-11 10:52:50 +02:00 · 2026-09-11 10:52:46 +02:00
260 changed files with 381 additions and 270 deletions
--- a/.claude/skills/hassio-addon-workflow/references/traps.md
+++ b/.claude/skills/hassio-addon-workflow/references/traps.md
@@ -70,10 +70,28 @@ service run scripts including `svc-xorg`, and Xvfb runs with `-vfbdevice /dev/dr

 - `00-global_var.sh` is cont-init **00**. Any cont-init script numbered higher runs *after* the
  injection, so it cannot change what a service will see through stage 2.
- LSIO's `svc-xorg` starts `#!/usr/bin/env bashio`, **not** `with-contenv`, so it never reads
-  stage 3 at all. Writing `container_environment` for it is a silent no-op — that shipped: the
-  file was written 6 seconds before Xvfb started, and Xvfb still came up at the base-image
-  default.
+- **Whether a service's own shebang still decides stage 3 depends on whether `ha_entrypoint.sh`
+  runs as PID 1** — i.e. whether the add-on replaces the base `ENTRYPOINT ["/init"]` with one that
+  makes `ha_entrypoint.sh` itself the container's entrypoint (live today in `ente` and
+  `free_games_claimer`; `wger` has the override written into its Dockerfile but commented out, so
+  it is not currently one of these — check the Dockerfile, not this list). Under the normal
+  `/init` path this script runs as the stage-2 hook, `$PID1` is false, and it never touches
+  `services.d/*/run` or `s6-overlay/s6-rc.d/*/run` at all (`.templates/ha_entrypoint.sh:430`,
+  gated on `if $PID1`) — s6's own stage 1 already created `/run/s6/container_environment` before
+  any cont-init script ran, so a service's shipped `with-contenv` shebang reads it normally.
+  Only the `ENTRYPOINT`-override path breaks this, and it breaks it twice over: s6 stage 1 never
+  runs, so nothing ever creates the envdir; and because `ha_entrypoint.sh` is now PID 1, it
+  rewrites the first line of every service `run` file to whichever shebang its own
+  `candidate_shebangs` probe landed on. That probe's first candidate,
+  `/command/with-contenv bashio`, fails precisely because the envdir was never created, so it
+  falls through to `/usr/bin/env bashio` for every service — the real mechanism behind the shipped
+  `svc-xorg` failure (its envdir file was written 6 seconds before Xvfb started, and Xvfb still
+  came up at the base-image default). `cont-init.d` scripts are a separate case: `run_one_script`
+  rewrites their shebang unconditionally, with no `$PID1` gate, so a cont-init script's own
+  shebang is never informative either way. `ha_entrypoint.sh` dumps the environment itself to
+  compensate for the missing envdir, and the envdir writes in `00-global_var.sh` /
+  `01-config_yaml.sh` are `if [ -d ]` guarded, so they take effect only once something has created
+  that directory.

 **Renaming an option to match a base-image env var moves validation out of your script and into
 the schema.** `00-global_var.sh` exports empty strings (only objects/arrays/nulls are dropped),
--- a/.templates/01-config_yaml.sh
+++ b/.templates/01-config_yaml.sh
@@ -19,7 +19,7 @@ slug="${slug#*_}"
 if [ ! -f /config/configuration.yaml ] && [ ! -f /config/configuration.json ]; then
    # New config location
    CONFIGLOCATION="/config"
-    CONFIGFILEBROWSER="/addon_configs/${HOSTNAME/-/_}/config.yaml"
+    CONFIGFILEBROWSER="/app_configs/${HOSTNAME/-/_}/config.yaml"
 else
    # Legacy config location
    CONFIGLOCATION="/config/addons_config/${slug}"
--- a/.templates/01-custom_script.sh
+++ b/.templates/01-custom_script.sh
@@ -174,7 +174,7 @@ slug="${slug#*_}"
 # Check type of config folder
 if [ ! -f /config/configuration.yaml ] && [ ! -f /config/configuration.json ]; then
  CONFIGLOCATION="/config"
-  CONFIGFILEBROWSER="/addon_configs/${HOSTNAME/-/_}/$slug.sh"
+  CONFIGFILEBROWSER="/app_configs/${HOSTNAME/-/_}/$slug.sh"
 else
  CONFIGLOCATION="/config/addons_autoscripts"
  CONFIGFILEBROWSER="/homeassistant/addons_autoscripts/$slug.sh"
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -70,7 +70,7 @@ version: "X.Y.Z"          # upstream version (format varies; see Versioning sect
 ingress: true/false
 ingress_port: 8000
 map:
-  - addon_config:rw        # /addon_configs/<hostname>/
+  - app_config:rw        # /app_configs/<hostname>/
  - share:rw
  - media:rw
  - ssl
--- a/addons_updater/CHANGELOG.md
+++ b/addons_updater/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 2026.08 (2026-08-01)

 - Addon versions written in config.yaml now always comply with Home Assistant versioning: an upstream tag Home Assistant cannot order (`version-bf9e0b4f`, `ubuntu-2026-06-01`, ...) or would sort as older (`1.2.3-2`, `1.2.3+4`) no longer lands in config.yaml. The addon number is incremented instead, while the raw upstream tag stays in updater.json so the same release is never published twice
@@ -31,7 +32,7 @@

 ## 3.19

- New HA config logic implemented. Files are now located in the addon config file, that can be accessed from the addon_configs folder from my filebrowser or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- New HA config logic implemented. Files are now located in the addon config file, that can be accessed from the app_configs folder from my filebrowser or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
 - Feat : if there is no releases in a github repo, check if there is a valid package and get the highest tag https://github.com/alexbelgium/hassio-addons/issues/1168
 - Feat : github_exclude applies to dockerhub

--- a/addons_updater/README.md
+++ b/addons_updater/README.md
@@ -115,7 +115,7 @@ verbose: "false"

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **Environment variables**: Use the add-on `env_vars` option and see [Add Environment Variables to your Addon](https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon) for details.
--- a/addons_updater/config.yaml
+++ b/addons_updater/config.yaml
@@ -8,7 +8,7 @@ environment:
 image: ghcr.io/alexbelgium/addons_updater-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
 name: Repository Updater
 options:
  date_iso8601: true
--- a/aurral/CHANGELOG.md
+++ b/aurral/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2.8.0 (2026-09-05)
 - Update to latest version from lklynet/aurral (changelog : https://github.com/lklynet/aurral/releases)
--- a/aurral/config.yaml
+++ b/aurral/config.yaml
@@ -21,7 +21,7 @@ ports_description:
 webui: http://[HOST]:[PORT:3001]

 map:
-  - addon_config:rw
+  - app_config:rw
  - share:rw
  - media:rw

--- a/baikal/CHANGELOG.md
+++ b/baikal/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 0.12.1 (2026-09-03)

 - Update to Baikal 0.12.1 from 0.10.1 (changelog : <https://github.com/sabre-io/Baikal/releases>). This includes the 0.12.1 fix for an XSS vulnerability that let an authenticated user take over the admin interface by renaming a calendar
@@ -28,7 +29,7 @@
 ## 0.9.5 (2024-04-27)
 - Update to latest version from ckulka/baikal-docker (changelog : https://github.com/ckulka/baikal-docker/releases)
 ## 0.9.4-3 (2024-04-26)
- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/baikal to a folder only accessible from my Filebrowser addon called /addon_configs/something-baikal. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/baikal to a folder only accessible from my Filebrowser addon called /app_configs/something-baikal. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/

 ## 0.9.4-2 (2024-01-14)

--- a/baikal/README.md
+++ b/baikal/README.md
@@ -50,7 +50,7 @@ Configurations can be done through the app webUI, except for the following optio

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **Environment variables**: See [Add Environment Variables to your Addon](https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon)
--- a/baikal/config.yaml
+++ b/baikal/config.yaml
@@ -66,7 +66,7 @@ devices:
  - /dev/nvme2
 image: ghcr.io/alexbelgium/baikal-{arch}
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - share:rw
  - ssl:ro
--- a/battybirdnet-pi/CHANGELOG.md
+++ b/battybirdnet-pi/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 2026.02.28 (28-02-2026)
 - Minor bugs fixed
 ## 2026.02.25-2 (25-02-2026)
--- a/battybirdnet-pi/README.md
+++ b/battybirdnet-pi/README.md
@@ -86,7 +86,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/battybirdnet-pi/config.yaml
+++ b/battybirdnet-pi/config.yaml
@@ -64,7 +64,7 @@ ingress: true
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
  - ssl
--- a/bazarr/CHANGELOG.md
+++ b/bazarr/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.

 ## 1.6.0.2 (2026-07-27)

@@ -26,7 +27,7 @@
 - Update to latest version from linuxserver/docker-bazarr (changelog : https://github.com/linuxserver/docker-bazarr/releases)

 ## 1.5.4-1 (2026-01-08)
- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/addons_config/bazarr to a folder only accessible from my Filebrowser addon called /addon_configs/xxx-bazarr. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/addons_config/bazarr to a folder only accessible from my Filebrowser addon called /app_configs/xxx-bazarr. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/

 ## 1.5.4 (2026-01-08)
 - Update to latest version from linuxserver/docker-bazarr (changelog : https://github.com/linuxserver/docker-bazarr/releases)
--- a/bazarr/config.yaml
+++ b/bazarr/config.yaml
@@ -76,7 +76,7 @@ ingress: true
 ingress_entry: bazarr
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - share:rw
  - media:rw
--- a/bazarr/rootfs/etc/cont-init.d/20-folders.sh
+++ b/bazarr/rootfs/etc/cont-init.d/20-folders.sh
@@ -23,7 +23,7 @@ fi
 slug=bazarr

 if [ -d "/homeassistant/addons_config/$slug" ]; then
-    echo "Migrating /homeassistant/addons_config/$slug to /addon_configs/xxx-$slug"
+    echo "Migrating /homeassistant/addons_config/$slug to /app_configs/xxx-$slug"
    cp -rnf /homeassistant/addons_config/"$slug"/. /config/ || true
    mv /homeassistant/addons_config/"$slug" /homeassistant/addons_config/"$slug"_migrated
 fi
--- a/birdnet-go-dev/CHANGELOG.md
+++ b/birdnet-go-dev/CHANGELOG.md
@@ -1,3 +1,7 @@
+## 20260910.2 (11-09-2026)
+- Minor bugs fixed
+## 20260910 (11-09-2026)
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 20260909.7 (10-09-2026)
 - Correct the "first daily detection consensus" README section (review feedback on PR #3056): a merged-upstream setting stays in the build rather than disappearing, every attempt for a species is held back until one is accepted rather than only the first, and the "known to every active bird model" exemption is scoped per audio source, matching the implementation.
 ## 20260909.6 (10-09-2026)
--- a/birdnet-go-dev/HAINTEGRATION.md
+++ b/birdnet-go-dev/HAINTEGRATION.md
@@ -25,7 +25,7 @@ MQTT password : Ri5ahV1aipeiw0aelerooteixai5ohtoeNg6oo3mo0thi5te0phiezuge4Phoore
 MQTT broker : tcp://core-mosquitto:1883
 ---

-Edit this section of config.yaml found in addon_configs/db21ed7f_birdnet-go/:
+Edit this section of config.yaml found in app_configs/db21ed7f_birdnet-go/:
    mqtt:
        enabled: true # true to enable MQTT
        broker: tcp://core-mosquitto:1883 # MQTT (tcp://host:port)
--- a/birdnet-go-dev/README.md
+++ b/birdnet-go-dev/README.md
@@ -114,7 +114,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/birdnet-go-dev/config.yaml
+++ b/birdnet-go-dev/config.yaml
@@ -80,7 +80,7 @@ ingress_entry: "ui/dashboard"
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
 name: Birdnet-go (customized and built from source)
@@ -127,5 +127,5 @@ slug: birdnet-go-dev
 udev: true
 url: https://github.com/alexbelgium/hassio-addons
 usb: true
-version: "20260909.7"
+version: "20260910.2"
 video: true
--- a/birdnet-go/CHANGELOG.md
+++ b/birdnet-go/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 20260827 (2026-08-29)
 - Update to latest version from tphakala/birdnet-go (changelog : https://github.com/tphakala/birdnet-go/releases)
--- a/birdnet-go/HAINTEGRATION.md
+++ b/birdnet-go/HAINTEGRATION.md
@@ -25,7 +25,7 @@ MQTT password : Ri5ahV1aipeiw0aelerooteixai5ohtoeNg6oo3mo0thi5te0phiezuge4Phoore
 MQTT broker : tcp://core-mosquitto:1883
 ---

-Edit this section of config.yaml found in addon_configs/db21ed7f_birdnet-go/:
+Edit this section of config.yaml found in app_configs/db21ed7f_birdnet-go/:
    mqtt:
        enabled: true # true to enable MQTT
        broker: tcp://core-mosquitto:1883 # MQTT (tcp://host:port)
--- a/birdnet-go/README.md
+++ b/birdnet-go/README.md
@@ -79,7 +79,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/birdnet-go/config.yaml
+++ b/birdnet-go/config.yaml
@@ -81,7 +81,7 @@ ingress_entry: "ui/dashboard"
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
 name: Birdnet-go
--- a/birdnet-pi-zach/CHANGELOG.md
+++ b/birdnet-pi-zach/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 2026.08.15 (15-08-2026)

 - Fix: `ALSA_CARD` now really selects the microphone. Its value was copied as-is into `REC_CARD`, but BirdNET-Pi hands `REC_CARD` to `arecord -D` / `ffmpeg -f alsa -i`, which expect an ALSA PCM name: a card index such as `1` gave `Unknown PCM 1` and no recording at all. It is now converted to `plughw:CARD=<value>,DEV=0`, while a value that already is a PCM name (`dsnoop:CARD=Audio,DEV=0`, `default`, `null`, `pulse`, `pipewire`, ...) is used as provided
--- a/birdnet-pi-zach/README.md
+++ b/birdnet-pi-zach/README.md
@@ -93,7 +93,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/birdnet-pi-zach/config.yaml
+++ b/birdnet-pi-zach/config.yaml
@@ -61,7 +61,7 @@ image: ghcr.io/alexbelgium/birdnet-pi-zach-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
  - ssl
--- a/birdnet-pi/CHANGELOG.md
+++ b/birdnet-pi/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 2026.08.15 (15-08-2026)

 - Fix: `ALSA_CARD` now really selects the microphone. Its value was copied as-is into `REC_CARD`, but BirdNET-Pi hands `REC_CARD` to `arecord -D` / `ffmpeg -f alsa -i`, which expect an ALSA PCM name: a card index such as `1` gave `Unknown PCM 1` and no recording at all. It is now converted to `plughw:CARD=<value>,DEV=0`, while a value that already is a PCM name (`dsnoop:CARD=Audio,DEV=0`, `default`, `null`, `pulse`, `pipewire`, ...) is used as provided
@@ -156,7 +157,7 @@
 - [ALL] Fix non-avx2 cpu support

 ## 2025.02.23 (2025-02-16)
- WARNING 2025.02.14/16 was buggy. If you installed it you need to restore a backup or delete manually your /addon_configs/xxx-birdnet-pi/birdnet.conf file and recreate it
+- WARNING 2025.02.14/16 was buggy. If you installed it you need to restore a backup or delete manually your /app_configs/xxx-birdnet-pi/birdnet.conf file and recreate it
 - Allow usage as a standalone container (thanks @gotschi) https://github.com/mcguirepr89/BirdNET-Pi/issues/211#issuecomment-2650095952
 - Corrected a bug preventing to create db
 - Corrected a bug to ensure the the most up-to-date birdnet.conf on fresh start
--- a/birdnet-pi/README.md
+++ b/birdnet-pi/README.md
@@ -93,7 +93,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/birdnet-pi/config.yaml
+++ b/birdnet-pi/config.yaml
@@ -61,7 +61,7 @@ image: ghcr.io/alexbelgium/birdnet-pi-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
  - ssl
--- a/birdnet-pipy/CHANGELOG.md
+++ b/birdnet-pipy/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 0.8.8 (2026-08-22)
 - Update to latest version from Suncuss/BirdNET-PiPy (changelog : https://github.com/Suncuss/BirdNET-PiPy/releases)
--- a/birdnet-pipy/README.md
+++ b/birdnet-pipy/README.md
@@ -47,7 +47,7 @@ This add-on supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This add-on supports custom scripts and environment variables through the `addon_config` mapping:
+This add-on supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/birdnet-pipy/config.yaml
+++ b/birdnet-pipy/config.yaml
@@ -67,7 +67,7 @@ ingress: true
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - ssl:rw
  - share:rw
 name: BirdNET-PiPy
--- a/browser_brave/CHANGELOG.md
+++ b/browser_brave/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 1.94.121-ls127 (2026-09-05)
 - Update to latest version from linuxserver/docker-brave (changelog : https://github.com/linuxserver/docker-brave/releases)
--- a/browser_brave/config.yaml
+++ b/browser_brave/config.yaml
@@ -26,7 +26,7 @@ image: ghcr.io/alexbelgium/brave-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
  - ssl
--- a/browser_chromium/CHANGELOG.md
+++ b/browser_chromium/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2026.09.05 (2026-09-05)
 - Update to latest version from linuxserver/docker-chromium (changelog : https://github.com/linuxserver/docker-chromium/releases)
--- a/browser_chromium/config.yaml
+++ b/browser_chromium/config.yaml
@@ -26,7 +26,7 @@ image: ghcr.io/alexbelgium/chromium-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
  - ssl
--- a/browserless_chrome/CHANGELOG.md
+++ b/browserless_chrome/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2.56.3 (2026-09-05)
 - Update to latest version from browserless/chrome (changelog : https://github.com/browserless/chrome/releases)
--- a/browserless_chrome/README.md
+++ b/browserless_chrome/README.md
@@ -50,7 +50,7 @@ TIMEOUT: 60000

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/browserless_chrome/config.yaml
+++ b/browserless_chrome/config.yaml
@@ -69,7 +69,7 @@ environment:
 image: ghcr.io/alexbelgium/browserless_chrome-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
 name: Browserless Chromium
 options:
  env_vars: []
--- a/calibre/CHANGELOG.md
+++ b/calibre/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 9.14.0 (2026-08-29)
 - Update to latest version from linuxserver/docker-calibre (changelog : https://github.com/linuxserver/docker-calibre/releases)
@@ -223,7 +224,7 @@

 - Update to latest version from linuxserver/docker-calibre
 - BREAKING CHANGE : please relink your library according to https://github.com/alexbelgium/hassio-addons/issues/1154#issuecomment-1879182729
- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/calibre to a folder only accessible from my Filebrowser addon called /addon_configs/something-calibre. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1154
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/calibre to a folder only accessible from my Filebrowser addon called /app_configs/something-calibre. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1154

 ## 7.2.0 (2023-12-16)

--- a/calibre/README.md
+++ b/calibre/README.md
@@ -98,7 +98,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/calibre/config.yaml
+++ b/calibre/config.yaml
@@ -78,7 +78,7 @@ init: false
 map:
  - media:rw
  - share:rw
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - ssl
 name: Calibre
--- a/calibre_web/CHANGELOG.md
+++ b/calibre_web/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 0.6.27.4 (2026-09-04)
 - Fix: Kobo sync could not be enabled, failing with "Kepubify binary not found" even when the path was set by hand. The LinuxServer base image installs the converter as `/usr/bin/kepubify` with `curl -o`, which leaves it mode 0644 and gives it a name calibre-web does not accept : `binary_helper.py` only takes `kepubify-linux-64bit` or `kepubify-linux-32bit`, and only when `os.access(X_OK)` passes. The addon now makes the binary executable and publishes it as `/opt/kepubify/kepubify-linux-64bit`, the directory calibre-web's own autodetection already probes, so the path is filled in without any manual step (https://github.com/alexbelgium/hassio-addons/issues/3040)
@@ -28,7 +29,7 @@
 - Update to latest version from linuxserver/docker-calibre-web (changelog : https://github.com/linuxserver/docker-calibre-web/releases)
 ## 0.6.24-10 (2025-05-28)
 - Fix migration script
- Allow access to Calibre folder through /addon_configs/xxx-Calibre
+- Allow access to Calibre folder through /app_configs/xxx-Calibre

 ## 0.6.24 (2024-11-23)
 - Update to latest version from linuxserver/docker-calibre-web (changelog : https://github.com/linuxserver/docker-calibre-web/releases)
@@ -44,7 +45,7 @@
 - Minor bugs fixed
 ## 0.6.21-5 (2024-01-12)

- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/calibre-web to a folder only accessible from my Filebrowser addon called /addon_configs/something-calibre-web. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1177
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/calibre-web to a folder only accessible from my Filebrowser addon called /app_configs/something-calibre-web. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1177

 ## 0.6.21-2 (2023-11-05)

--- a/calibre_web/config.yaml
+++ b/calibre_web/config.yaml
@@ -77,8 +77,8 @@ image: ghcr.io/alexbelgium/calibre_web-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
-  - all_addon_configs:rw
+  - app_config:rw
+  - all_app_configs:rw
  - homeassistant_config:rw
  - media:rw
  - share:rw
--- a/claude_desktop/CHANGELOG.md
+++ b/claude_desktop/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 07308545.6 (2026-09-05)
 - Update to latest version from aaddrick/claude-desktop-debian (changelog : https://github.com/aaddrick/claude-desktop-debian/releases)
--- a/claude_desktop/SIGN_IN.md
+++ b/claude_desktop/SIGN_IN.md
@@ -63,7 +63,7 @@ magic link into the in-session Chromium (not a phone).
 - Add-on Configuration → `additional_apps: chromium`, restart (installed by
  `rootfs/etc/cont-init.d/80-configuration.sh`).
 - Add the two `xdg-settings`/`xdg-mime` commands to the custom script
-  `/addon_configs/db21ed7f_claude-desktop/claude_desktop.sh` (the image ships no standalone
+  `/app_configs/db21ed7f_claude-desktop/claude_desktop.sh` (the image ships no standalone
  terminal).

 ---
--- a/claude_desktop/config.yaml
+++ b/claude_desktop/config.yaml
@@ -34,7 +34,7 @@ hassio_role: manager
 homeassistant_api: true
 auth_api: true
 map:
-  - addon_config:rw
+  - app_config:rw
  - share:rw
  - media:rw
  - ssl
--- a/cleanuparr/CHANGELOG.md
+++ b/cleanuparr/CHANGELOG.md
@@ -1,3 +1,5 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
+- Fix persistent data directory: the entrypoint now writes to the `/config` mount (the container-side path of the `app_config` map) instead of an unmounted `/app_configs/cleanuparr` path, so Cleanuparr's data survives container recreation.
 
 ## 2.10.5 (2026-08-13)
 - Update to latest version from Cleanuparr/Cleanuparr (changelog : https://github.com/Cleanuparr/Cleanuparr/releases)
--- a/cleanuparr/Dockerfile
+++ b/cleanuparr/Dockerfile
@@ -63,7 +63,7 @@ COPY bashio-standalone.sh /usr/local/lib/bashio-standalone.sh
 RUN chmod 0755 /usr/local/lib/bashio-standalone.sh

 # Bypass the original /entrypoint.sh (which mounts /config as VOLUME).
-# Our wrapper symlinks /app/config → HA addon_config and starts ./Cleanuparr directly.
+# Our wrapper symlinks /app/config → HA app_config and starts ./Cleanuparr directly.
 ENTRYPOINT ["/ha_entrypoint.sh"]
 CMD ["./Cleanuparr"]

--- a/cleanuparr/config.yaml
+++ b/cleanuparr/config.yaml
@@ -71,7 +71,7 @@ ingress_stream: true
 init: false
 panel_icon: mdi:movie-search
 map:
-  - addon_config:rw
+  - app_config:rw
 name: Cleanuparr
 options:
  env_vars: []
--- a/cleanuparr/rootfs/ha_entrypoint.sh
+++ b/cleanuparr/rootfs/ha_entrypoint.sh
@@ -5,7 +5,7 @@ set -e
 ###############################################################################
 # Home Assistant Addon entrypoint for Cleanuparr
 # The .NET app uses /app/config as its data directory.
-# We symlink /app/config → /addon_configs/cleanuparr (HA persistent storage)
+# We symlink /app/config → /config (the HA app_config mount, HA persistent storage)
 # and start ./Cleanuparr directly, bypassing the original /entrypoint.sh
 # which would trigger the /config Docker VOLUME mount.
 ###############################################################################
@@ -26,7 +26,7 @@ if [ -d /etc/cont-init.d ]; then
 fi

 # ─── Setup persistent data directory ─────────────────────────────────────────
-HA_DATA_DIR="/addon_configs/cleanuparr"
+HA_DATA_DIR="/config"
 echo "[Cleanuparr] Setting up data directory: $HA_DATA_DIR"
 mkdir -p "$HA_DATA_DIR"

--- a/cloudcommander/CHANGELOG.md
+++ b/cloudcommander/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 19.20.5 (2026-09-05)
 - Update to latest version from coderaiser/cloudcmd (changelog : https://github.com/coderaiser/cloudcmd/releases)
@@ -234,7 +235,7 @@
 ## 16.17.7-3 (2023-11-19)

 - Minor bugs fixed
- MAJOR CHANGE : new HA config logic implemented. Files are now located in the addon config file, that can be accessed from the addon_configs folder from my cloudcommander or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- MAJOR CHANGE : new HA config logic implemented. Files are now located in the addon config file, that can be accessed from the app_configs folder from my cloudcommander or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
 - Homeassistant config accessible in /homeassistant folder ; all addons config in /addons_config ; this addon config in /config

 ## 16.17.7-2 (2023-10-30)
--- a/cloudcommander/config.yaml
+++ b/cloudcommander/config.yaml
@@ -69,8 +69,8 @@ image: ghcr.io/alexbelgium/cloudcommander-{arch}
 ingress: true
 ingress_stream: true
 map:
-  - addon_config:rw
-  - all_addon_configs:rw
+  - app_config:rw
+  - all_app_configs:rw
  - homeassistant_config:rw
  - ssl:rw
  - share:rw
--- a/cloudcommander/rootfs/etc/cont-init.d/99-run.sh
+++ b/cloudcommander/rootfs/etc/cont-init.d/99-run.sh
@@ -35,7 +35,7 @@ fi
 # Create symlinks with legacy folders
 if [ -d /homeassistant/addons_config ]; then
    ln -s /homeassistant/addons_config /config
-    find /addon_configs/ -maxdepth 1 -mindepth 1 -type d -not -name "*cloudcommander*" -exec ln -s {} /config/addons_config/ \;
+    find /app_configs/ -maxdepth 1 -mindepth 1 -type d -not -name "*cloudcommander*" -exec ln -s {} /config/addons_config/ \;
 fi
 if [ -d /homeassistant/addons_autoscripts ]; then
    ln -s /homeassistant/addons_autoscripts /config
--- a/codex/CHANGELOG.md
+++ b/codex/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2.2.11 (2026-08-29)
 - Update to latest version from ajslater/codex (changelog : https://github.com/ajslater/codex/releases)
--- a/codex/README.md
+++ b/codex/README.md
@@ -91,7 +91,7 @@ cifsdomain: "WORKGROUP"

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/codex/config.yaml
+++ b/codex/config.yaml
@@ -65,7 +65,7 @@ image: ghcr.io/alexbelgium/codex-{arch}
 ingress: true
 ingress_stream: true
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
 name: Codex
--- a/collabora/CHANGELOG.md
+++ b/collabora/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 26.04.3.2.1 (2026-09-05)
 - Update to latest version from collabora/code
--- a/collabora/README.md
+++ b/collabora/README.md
@@ -138,7 +138,7 @@ The two hostnames have different roles, and swapping them is the most common cau

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/collabora/config.yaml
+++ b/collabora/config.yaml
@@ -8,7 +8,7 @@ environment:
 image: ghcr.io/alexbelgium/collabora-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - ssl:ro
 name: Collabora
 options:
--- a/comixed/CHANGELOG.md
+++ b/comixed/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 - 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.

 ## 1.3 (2024-03-11)
--- a/comixed/config.yaml
+++ b/comixed/config.yaml
@@ -59,7 +59,7 @@ hassio_api: true
 homeassistant_api: true
 image: ghcr.io/alexbelgium/comixed-{arch}
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
  - share:rw
 name: Comixed
--- a/emby/CHANGELOG.md
+++ b/emby/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.

 ## 4.9.5.0 (2026-05-19)
 - Update to latest version from linuxserver/docker-emby (changelog : https://github.com/linuxserver/docker-emby/releases)
@@ -14,7 +15,7 @@
 ## 4.8.11.0-2 (2025-08-02)
 - Minor bugs fixed
 ## 4.8.11.0 (2025-04-22)
- WARNING : migration of config to addon_config instead of homeassistant config folder. Allows automatic backups. The location of the database however is not changed.
+- WARNING : migration of config to app_config instead of homeassistant config folder. Allows automatic backups. The location of the database however is not changed.

 ## 4.9.0.48 (2025-04-19)
 - Update to latest version from linuxserver/docker-emby (changelog : https://github.com/linuxserver/docker-emby/releases)
--- a/emby/config.yaml
+++ b/emby/config.yaml
@@ -79,7 +79,7 @@ ingress_port: 0
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - share:rw
  - media:rw
  - ssl:rw
--- a/emby_beta/CHANGELOG.md
+++ b/emby_beta/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 4.10.0.30 (2026-09-05)
 - Update to latest version from linuxserver/docker-emby (changelog : https://github.com/linuxserver/docker-emby/releases)
@@ -172,7 +173,7 @@
 ## 4.9.0.50 (2025-04-26)

 - Update to latest version from linuxserver/docker-emby (changelog : https://github.com/linuxserver/docker-emby/releases)
- WARNING : migration of config to addon_config instead of homeassistant config folder. Allows automatic backups. The location of the database however is not changed.
+- WARNING : migration of config to app_config instead of homeassistant config folder. Allows automatic backups. The location of the database however is not changed.

 ## 4.9.0.48 (2025-04-19)

--- a/emby_beta/config.yaml
+++ b/emby_beta/config.yaml
@@ -79,7 +79,7 @@ ingress_port: 0
 ingress_stream: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - share:rw
  - media:rw
--- a/ente/CHANGELOG.md
+++ b/ente/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 4.4.27 (2026-09-05)
 - Update to latest version from ente/ente (changelog : https://github.com/ente/ente/releases)
--- a/ente/README.md
+++ b/ente/README.md
@@ -79,7 +79,7 @@ TZ: "America/New_York"

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/ente/config.yaml
+++ b/ente/config.yaml
@@ -76,7 +76,7 @@ environment:
 image: ghcr.io/alexbelgium/ente-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
 name: Ente
 options:
  env_vars: []
--- a/filebrowser/CHANGELOG.md
+++ b/filebrowser/CHANGELOG.md
@@ -1,3 +1,5 @@
+- Breaking change : only appears in ingress for admins
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2.63.23 (2026-08-01)
 - Update to latest version from filebrowser/filebrowser (changelog : https://github.com/filebrowser/filebrowser/releases)
@@ -241,7 +243,7 @@

 ## 2.23.0_reverted5 (2023-11-21)

- MAJOR CHANGE : new HA config logic implemented. Files are now located in the addon config file, that can be accessed from the addon_configs folder from my filebrowser or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- MAJOR CHANGE : new HA config logic implemented. Files are now located in the addon config file, that can be accessed from the app_configs folder from my filebrowser or cloudcommander addons. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
 - Homeassistant config accessible in /homeassistant folder ; all addons config in /addons_config ; this addon config in /config

 ## 2.23.0_reverted (2023-09-29)
--- a/filebrowser/README.md
+++ b/filebrowser/README.md
@@ -108,7 +108,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/filebrowser/config.yaml
+++ b/filebrowser/config.yaml
@@ -81,9 +81,9 @@ ingress_entry: files
 ingress_port: 8071
 ingress_stream: true
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
-  - all_addon_configs:rw
+  - all_app_configs:rw
  - homeassistant_config:rw
  - addons:rw
  - backup:rw
@@ -98,7 +98,7 @@ options:
  follow_external_symlinks: true
  keyfile: privkey.pem
  ssl: false
-panel_admin: false
+panel_admin: true
 panel_icon: mdi:file-search
 ports:
  8080/tcp: 8071
--- a/filebrowser/rootfs/etc/cont-init.d/20-folders.sh
+++ b/filebrowser/rootfs/etc/cont-init.d/20-folders.sh
@@ -35,7 +35,7 @@ fi
 # Create symlinks with legacy folders
 if [ -d /homeassistant/addons_config ]; then
    ln -s /homeassistant/addons_config /config
-    find /addon_configs/ -maxdepth 1 -mindepth 1 -type d -not -name "*filebrowser*" -exec ln -s {} /config/addons_config/ \;
+    find /app_configs/ -maxdepth 1 -mindepth 1 -type d -not -name "*filebrowser*" -exec ln -s {} /config/addons_config/ \;
 fi
 if [ -d /homeassistant/addons_autoscripts ]; then
    ln -s /homeassistant/addons_autoscripts /config
--- a/filebrowser_quantum/CHANGELOG.md
+++ b/filebrowser_quantum/CHANGELOG.md
@@ -1,3 +1,5 @@
+- Breaking change : only appears in ingress for admins
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 1.5.6 (2026-09-05)
 - Update to latest version from gtsteffaniak/filebrowser (changelog : https://github.com/gtsteffaniak/filebrowser/releases)
--- a/filebrowser_quantum/README.md
+++ b/filebrowser_quantum/README.md
@@ -85,7 +85,7 @@ This addon supports mounting both local drives and remote SMB shares:

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-add-ons
--- a/filebrowser_quantum/config.yaml
+++ b/filebrowser_quantum/config.yaml
@@ -82,9 +82,9 @@ ingress: true
 ingress_port: 8071
 ingress_stream: true
 map:
-  - addon_config:rw
+  - app_config:rw
  - media:rw
-  - all_addon_configs:rw
+  - all_app_configs:rw
  - homeassistant_config:rw
  - addons:rw
  - backup:rw
@@ -95,7 +95,7 @@ options:
  env_vars: []
  auth_method: noauth
  default_user_scope: "/"
-panel_admin: false
+panel_admin: true
 panel_icon: mdi:file-search
 ports:
  8072/tcp: 8071
--- a/fireflyiii_data_importer/CHANGELOG.md
+++ b/fireflyiii_data_importer/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 2.3.4 (2026-07-04)
 - Update to latest version from firefly-iii/data-importer (changelog : https://github.com/firefly-iii/data-importer/releases)
@@ -193,7 +194,7 @@

 ## 1.4.5-2 (2024-03-28)

- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/fireflyiii_date_importer in a folder only accessible from my Filebrowser addon called /addon_configs/db21ed7f_fireflyiii_date_importer. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/fireflyiii_date_importer in a folder only accessible from my Filebrowser addon called /app_configs/db21ed7f_fireflyiii_date_importer. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/

 ## 1.4.5 (2024-03-23)

--- a/fireflyiii_data_importer/README.md
+++ b/fireflyiii_data_importer/README.md
@@ -78,11 +78,11 @@ silent: false

 ### File Locations

- **Configurations**: `/addon_configs/xxx-fireflyiii_data_importer/configurations/`
+- **Configurations**: `/app_configs/xxx-fireflyiii_data_importer/configurations/`
  - Store import configuration files here
  - See: https://docs.firefly-iii.org/data-importer/help/config/

- **Import Files**: `/addon_configs/xxx-fireflyiii_data_importer/import_files/`
+- **Import Files**: `/app_configs/xxx-fireflyiii_data_importer/import_files/`
  - Place CSV files here for automatic importing
  - See: https://docs.firefly-iii.org/data-importer/usage/command_line/

@@ -95,7 +95,7 @@ silent: false

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/fireflyiii_data_importer/config.yaml
+++ b/fireflyiii_data_importer/config.yaml
@@ -69,7 +69,7 @@ environment:
 image: ghcr.io/alexbelgium/fireflyiii_data_importer-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - share:rw
  - ssl
--- a/free_games_claimer/CHANGELOG.md
+++ b/free_games_claimer/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 2.1.0 (2026-08-24)

 - Updated the pinned upstream from Free Games Claimer Remaster 1.1 to 1.6,
--- a/free_games_claimer/README.md
+++ b/free_games_claimer/README.md
@@ -71,7 +71,7 @@ scheduler. Set `SCHEDULER_HOURS` in `config.env` to control the interval.

 The add-on keeps its configuration in `CONFIG_LOCATION`, which defaults to
 `/config/config.env`. From Home Assistant this is stored in the add-on's
-private `addon_configs` directory and can be edited with a compatible file
+private `app_configs` directory and can be edited with a compatible file
 browser add-on.

 A template is created on first start. Common examples are:
--- a/free_games_claimer/config.yaml
+++ b/free_games_claimer/config.yaml
@@ -70,7 +70,7 @@ environment:
 image: ghcr.io/alexbelgium/free_games_claimer-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
 name: Free Games Claimer
 options:
--- a/free_games_claimer/rootfs/etc/cont-init.d/00-migrate_files.sh
+++ b/free_games_claimer/rootfs/etc/cont-init.d/00-migrate_files.sh
@@ -5,7 +5,7 @@ slug="free_games_claimer"
 if [ -f "/homeassistant/addons_config/$slug/config.yaml" ] && [ ! -f "/homeassistant/addons_config/$slug/migrated" ]; then
    bashio::log.warning "Migrating config.yaml"
    mv "/homeassistant/addons_config/$slug"/* /config/ || true
-    echo "Migrated to internal config folder accessible at /addon_configs/xxx-$slug" > "/homeassistant/addons_config/$slug/migrated"
+    echo "Migrated to internal config folder accessible at /app_configs/xxx-$slug" > "/homeassistant/addons_config/$slug/migrated"
 fi

 if [ -f "/homeassistant/addons_autoscripts/$slug.sh" ]; then
--- a/gitea/CHANGELOG.md
+++ b/gitea/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 1.27.3 (2026-09-05)
 - Update to latest version from go-gitea/gitea (changelog : https://github.com/go-gitea/gitea/releases)
@@ -19,7 +20,7 @@
 - Minor bugs fixed

 ## 1.26.2-2 (2026-06-19)
- Expose app.ini in the addon_config folder so users can edit it directly via the HA file editor
+- Expose app.ini in the app_config folder so users can edit it directly via the HA file editor

 ## 1.26.2-1 (2026-06-19)
 - Fix SSH authentication failing with `chroot("/var/empty"): Operation not permitted [preauth]` by allowing `capability sys_chroot` in the AppArmor profile, which sshd needs for privilege-separation (#2653)
--- a/gitea/README.md
+++ b/gitea/README.md
@@ -63,16 +63,16 @@ ROOT_URL: "http://homeassistant.local:3000"

 ### Direct app.ini Access

-The Gitea `app.ini` configuration file is exposed in the add-on's config folder (`/addon_configs/gitea/app.ini` on the host), making it directly editable via the HA file editor or Studio Code add-on.
+The Gitea `app.ini` configuration file is exposed in the add-on's config folder (`/app_configs/gitea/app.ini` on the host), making it directly editable via the HA file editor or Studio Code add-on.

- **On first run**: complete the Gitea setup wizard, then restart the add-on. The generated `app.ini` will be copied to the addon_config folder automatically.
- **On subsequent runs**: edit `/addon_configs/gitea/app.ini` directly for any Gitea setting not covered by the options above. The add-on options (SSL, DOMAIN, ROOT_URL, APP_NAME) are still applied on top of your file each restart.
+- **On first run**: complete the Gitea setup wizard, then restart the add-on. The generated `app.ini` will be copied to the app_config folder automatically.
+- **On subsequent runs**: edit `/app_configs/gitea/app.ini` directly for any Gitea setting not covered by the options above. The add-on options (SSL, DOMAIN, ROOT_URL, APP_NAME) are still applied on top of your file each restart.

 See the [Gitea configuration cheat sheet](https://docs.gitea.com/administration/config-cheat-sheet) for all available options.

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/gitea/config.yaml
+++ b/gitea/config.yaml
@@ -67,7 +67,7 @@ devices:
 image: ghcr.io/alexbelgium/gitea-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - share:rw
  - ssl:rw
 name: Gitea
--- a/gitea/rootfs/etc/cont-init.d/99-run.sh
+++ b/gitea/rootfs/etc/cont-init.d/99-run.sh
@@ -14,17 +14,17 @@ mkdir -p /data/gitea/conf
 # case where Gitea's atomic SaveTo replaces the symlink with the completed config.
 # Always overwrite /config/app.ini so the installed settings are never discarded.
 if [ -f "/data/gitea/conf/app.ini" ] && [ ! -L "/data/gitea/conf/app.ini" ]; then
-    bashio::log.info "Moving app.ini to addon_config folder for direct access"
+    bashio::log.info "Moving app.ini to app_config folder for direct access"
    cp /data/gitea/conf/app.ini /config/app.ini
    rm /data/gitea/conf/app.ini
 fi

 # Symlink /data/gitea/conf/app.ini -> /config/app.ini so the file is visible in the
-# addon_config folder (accessible via the HA file editor). When Gitea's first-run
+# app_config folder (accessible via the HA file editor). When Gitea's first-run
 # wizard writes the config it lands in /config/app.ini via this symlink.
 if [ ! -L "/data/gitea/conf/app.ini" ]; then
    ln -s /config/app.ini /data/gitea/conf/app.ini
-    bashio::log.info "app.ini is now accessible in your addon_config folder"
+    bashio::log.info "app.ini is now accessible in your app_config folder"
 fi

 for file in /config/app.ini /etc/templates/app.ini; do
--- a/grampsweb/CHANGELOG.md
+++ b/grampsweb/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 26.8.1 (2026-08-29)
 - Update to latest version from gramps-project/gramps-web (changelog : https://github.com/gramps-project/gramps-web/releases)
--- a/grampsweb/README.md
+++ b/grampsweb/README.md
@@ -94,7 +94,7 @@ GRAMPSWEB_DEFAULT_FROM_EMAIL: "gramps@example.com"

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/grampsweb/config.yaml
+++ b/grampsweb/config.yaml
@@ -83,7 +83,7 @@ options:
  keyfile: privkey.pem
  ssl: false
 map:
-  - type: addon_config
+  - type: app_config
    read_only: false
  - type: ssl
    read_only: true
--- a/guacamole/CHANGELOG.md
+++ b/guacamole/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 ## 1.6.0-bullseye-3 (13-03-2026)
 - Fix PROXY_ALLOWED_IPS_REGEX default from invalid regex "*" to ".*"

@@ -49,7 +50,7 @@
 ## TEST2 (2024-03-18)
 - Minor bugs fixed
 ## TEST1 (2024-03-17)
- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/guacamole to a folder only accessible from my Filebrowser addon called /addon_configs/something-guacamole. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1309
+- ⚠ MAJOR CHANGE : switch to the new config logic from homeassistant. Your configuration files will have migrated from /config/hassio_addons/guacamole to a folder only accessible from my Filebrowser addon called /app_configs/something-guacamole. This avoids the addon to mess with your homeassistant configuration folder, and allows to backup the options. Migration of data, custom configs, and custom scripts should be automatic. Please be sure to update all your links however ! For more information, see here : https://developers.home-assistant.io/blog/2023/11/06/public-addon-config/ https://github.com/alexbelgium/hassio-addons/issues/1309

 ## testnoupload (2023-11-11)

--- a/guacamole/README.md
+++ b/guacamole/README.md
@@ -63,7 +63,7 @@ The addon automatically configures a PostgreSQL database for storing Guacamole c

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/guacamole/config.yaml
+++ b/guacamole/config.yaml
@@ -76,7 +76,7 @@ image: ghcr.io/alexbelgium/guacamole-{arch}
 ingress: true
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - homeassistant_config:rw
  - media:rw
  - share:rw
--- a/immich/CHANGELOG.md
+++ b/immich/CHANGELOG.md
@@ -1,3 +1,4 @@
+- Migrate legacy add-on configuration map names to current app configuration terminology.
 
 ## 3.1.0.1 (2026-08-17)
 - Fix `password authentication failed for user` when `DB_PASSWORD` contains special characters. Passwords are now URI-encoded before being used in the psql connection string, and SQL-escaped before being used in `CREATE`/`ALTER USER` statements
@@ -211,7 +212,7 @@
 - NEW FUNCTION : allow to define a library path outside of the data location. For example, if you specify /mnt/NAS/MyPictures as "library_location", and /mnt/NAS/Immich as "data_location", it will then create the whole structure in /mnt/NAS/Immich including the /mnt/NAS/Immich/library. However, this will just be a symlink to /mnt/NAS/MyPictures ; allowing people to still manage their hard drives in a more linear manner
 - Ensure host is reachable before starting
 - Autocorrect homeassistant.local to local ip
- Align configuration with /addon_configs
+- Align configuration with /app_configs
 - Add gpu access

 ## 1.126.1 (2025-02-15)
@@ -383,7 +384,7 @@
 - Update to latest version from imagegenius/docker-immich
 - &#9888; PLEASE BACKUP before updating! Non reversible changes
 - &#9888; BREAKING change : dependency on the update postgres image for vector.rs support, it will not work if you do not update postgres !
- &#9888; Database location changed from /data to /addon_configs/xxx-postgres : no expected user impact other that all configuration files will also be located in this folder accessible with addons such as Filebrowser
+- &#9888; Database location changed from /data to /app_configs/xxx-postgres : no expected user impact other that all configuration files will also be located in this folder accessible with addons such as Filebrowser

 ## 1.90.2 (2023-12-09)

--- a/immich/README.md
+++ b/immich/README.md
@@ -113,7 +113,7 @@ data_location: "/mnt/sda1/immich"

 ### Custom Scripts and Environment Variables

-This addon supports custom scripts and environment variables through the `addon_config` mapping:
+This addon supports custom scripts and environment variables through the `app_config` mapping:

 - **Custom scripts**: See [Running Custom Scripts in Addons](https://github.com/alexbelgium/hassio-addons/wiki/Running-custom-scripts-in-Addons)
 - **env_vars option**: Use the add-on `env_vars` option to pass extra environment variables (uppercase or lowercase names). See https://github.com/alexbelgium/hassio-addons/wiki/Add-Environment-variables-to-your-Addon-2 for details.
--- a/immich/config.yaml
+++ b/immich/config.yaml
@@ -85,7 +85,7 @@ hassio_api: true
 image: ghcr.io/alexbelgium/immich-{arch}
 init: false
 map:
-  - addon_config:rw
+  - app_config:rw
  - backup:rw
  - homeassistant_config:rw
  - media:rw
--- a/immich/rootfs/etc/cont-init.d/01-migrate.sh
+++ b/immich/rootfs/etc/cont-init.d/01-migrate.sh
@@ -11,11 +11,11 @@ if [ -f /homeassistant/addons_config/"$PREVIOUS_FOLDER"/config.yaml ]; then
    cp -rnp /homeassistant/addons_config/"$PREVIOUS_FOLDER"/ /config/
    mv /homeassistant/addons_config/"$PREVIOUS_FOLDER" "$PREVIOUS_FOLDER"_migrated
    if [ -d /config/addons_config ]; then rm -r /config/addons_config; fi
-    echo "Files moved to /addon_configs/$HOSTNAME"
+    echo "Files moved to /app_configs/$HOSTNAME"
 fi

 # Move autoscript
 if [ -f /homeassistant/addons_autoscrips/immich.sh ]; then
    cp -rnf /homeassistant/addons_autoscrips/"$PREVIOUS_FOLDER".sh /config/ &> /dev/null || true
-    bashio::log.yellow "... moved $PREVIOUS_FOLDER.sh from /config/addons_autoscripts to /addon_configs/$HOSTNAME"
+    bashio::log.yellow "... moved $PREVIOUS_FOLDER.sh from /config/addons_autoscripts to /app_configs/$HOSTNAME"
 fi
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
github-actions	9643ca35a3	GitHub bot: changelog [nobuild]	2026-09-11 09:46:01 +00:00
Alexandre	ce2d729e1b	Update config.yaml	2026-09-11 11:37:14 +02:00
github-actions	8ce92d80e2	GitHub bot: changelog [nobuild]	2026-09-11 08:53:41 +00:00
Alexandre	d247ed88b4	Update CHANGELOG.md	2026-09-11 10:52:50 +02:00
Alexandre	c9b5c54545	Document breaking change in CHANGELOG Added a breaking change note for admin ingress visibility.	2026-09-11 10:52:46 +02:00
Alexandre	07c6d1ca5d	Document breaking change in CHANGELOG.md Added a note about a breaking change for admins.	2026-09-11 10:52:21 +02:00
Alexandre	972f2c02b8	nobuild	2026-09-11 10:51:47 +02:00
Alexandre	58949cb09a	nobuild	2026-09-11 10:51:44 +02:00
Alexandre	8043104f30	Update config.yaml	2026-09-11 10:43:26 +02:00
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
Alexandre	d60f17685e	skill(hassio-addon-workflow): fix the stage-3 trap's actual mechanism (#3058 ) * skill(hassio-addon-workflow): fix the stage-3 trap's actual mechanism traps.md attributed the shipped svc-xorg failure to that service's own shebang ("starts #!/usr/bin/env bashio, not with-contenv"). Verified against .templates/ha_entrypoint.sh: that isn't what decides it. ha_entrypoint.sh rewrites the first line of every cont-init.d script and every services.d/s6-rc.d run script to one shebang chosen by probing candidate_shebangs in order. The first candidate is /command/with-contenv bashio; in add-ons that override the base ENTRYPOINT ["/init"] (confirmed live in ente, wger, free_games_claimer), s6 stage 1 never runs, that candidate fails, and the probe falls through to /usr/bin/env bashio for every service in the image, regardless of what shebang it shipped with. So no service reads stage 3 in that case, not just svc-xorg. Surfaced independently by two agents in an unrelated eval run for PR #3057 (both named the rewrite; neither had the conditionality right), then verified against the script and confirmed the ENTRYPOINT-override path is real rather than hypothetical before writing this. No add-on touched; references/ only. markdownlint clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> * skill(hassio-addon-workflow): scope the stage-3 trap to the PID-1-entrypoint path Flagged by both Codex and Copilot, reproduced against .templates/ha_entrypoint.sh before accepting. The previous commit's fix still overclaimed: it said ha_entrypoint.sh rewrites every service's shebang, universally. It doesn't. The services.d/s6-rc.d rewrite loop is gated on `if $PID1` (line 430) — it only runs when ha_entrypoint.sh itself is the container's PID 1, i.e. when the add-on replaces the base ENTRYPOINT ["/init"]. Under the normal /init path (the overwhelming majority of add-ons), ha_entrypoint.sh runs as the stage-2 hook with PID1=false, never touches service run files, s6's own stage 1 already created container_environment before any cont-init script ran, and a service's shipped with-contenv shebang reads it normally — the opposite of what the previous wording implied. cont-init.d scripts are unconditional either way (run_one_script has no $PID1 gate), so a cont-init script's own shebang was never informative and that half stands. Also fixed: the previous commit named wger as a live example of the ENTRYPOINT override. Copilot caught that wger's override is written into its Dockerfile but commented out — confirmed (`grep '^#ENTRYPOINT' wger/Dockerfile`). Only ente and free_games_claimer currently have it active; wger dropped from the list. markdownlint clean; no add-on touched. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: BirdNET-Go Addon Builder <addon-builder@users.noreply.github.com> Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 08:05:29 +02:00