From a36751b7ca86fbd81dbda82c79b207d4919c6f0b Mon Sep 17 00:00:00 2001 From: padriano Date: Thu, 4 Jun 2026 14:41:42 +0100 Subject: [PATCH] retarget HA upgrade plan to 2026.5.4 (latest 2026.5 patch) Co-Authored-By: Claude Opus 4.8 (1M context) --- plans/Plan-HA-upgrade.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/plans/Plan-HA-upgrade.md b/plans/Plan-HA-upgrade.md index 2ec163b..f02b4ed 100644 --- a/plans/Plan-HA-upgrade.md +++ b/plans/Plan-HA-upgrade.md @@ -1,4 +1,4 @@ -# Home Assistant Upgrade Plan: 2024.5.4 → 2026.5.0 (revised) +# Home Assistant Upgrade Plan: 2024.5.4 → 2026.5.4 (revised) Direct jump (no intermediate version stops). Two structural compose changes are folded into this upgrade: bump the `image:` tag, and swap the healthcheck endpoint to one that doesn't require auth on modern HA. @@ -9,8 +9,8 @@ Direct jump (no intermediate version stops). Two structural compose changes are ## Target versions (as of May 2026) -- Core: `2026.5.0` (released May 6, 2026) -- Frontend: `20260325.6` (stable) — bundled inside the core image, no separate action needed +- Core: `2026.5.4` (released May 22, 2026) — the final/latest patch of the 2026.5 line (there is no 2026.5.5; 2026.6.0 shipped June 3, 2026). Bug-fix-only over 2026.5.0, so no additional breaking changes vs. that release. +- Frontend: bundled inside the core image, version tracks the chosen core tag — no separate action needed ## Scope @@ -125,7 +125,7 @@ Two changes to the `homeassistant` service: ```yaml homeassistant: - image: homeassistant/home-assistant:2026.5.0 # was 2024.5.4 + image: homeassistant/home-assistant:2026.5.4 # was 2024.5.4 ... healthcheck: test: ["CMD", "curl", "-fsSL", "http://localhost:8123/manifest.json"] # was /api/ (now requires auth) @@ -173,7 +173,7 @@ docker compose up -d homeassistant ```bash docker exec homeassistant python -c "from homeassistant.const import __version__; print(__version__)" - # expected: 2026.5.0 + # expected: 2026.5.4 ``` - **Local HTTP**: @@ -191,7 +191,7 @@ docker compose up -d homeassistant ## 7. Rollback -**Decide which option by where the upgrade failed.** Once 2026.5.0 has booted successfully it migrates the recorder DB schema *and* `.storage/` to the new format, and HA does **not** support schema downgrade. So whether reverting the image tag alone is safe depends entirely on whether migration started — check the HA log (step 6) for `Database upgrade in progress`: +**Decide which option by where the upgrade failed.** Once 2026.5.4 has booted successfully it migrates the recorder DB schema *and* `.storage/` to the new format, and HA does **not** support schema downgrade. So whether reverting the image tag alone is safe depends entirely on whether migration started — check the HA log (step 6) for `Database upgrade in progress`: - **Migration never started** (new container crashed/failed early, you never saw that line) → the on-disk config is untouched. Use **Option A** (revert tag only). - **Migration started or completed** (you saw that line, or HA reached the UI) → the DB/`.storage/` are now on the new schema. **Option A will fail** — old core will refuse the newer recorder schema. Use **Option B** (restore the config backup). @@ -218,7 +218,7 @@ Revert the image tag and healthcheck per Option A, then restore the pre-upgrade ```bash docker compose stop homeassistant -mv /home/padriano/projects/ha/config /home/padriano/projects/ha/config.failed-2026.5.0 # keep the failed state for diagnosis instead of rm -rf +mv /home/padriano/projects/ha/config /home/padriano/projects/ha/config.failed-2026.5.4 # keep the failed state for diagnosis instead of rm -rf cp -a /home/padriano/projects/ha/config.bak-2024.5.4 /home/padriano/projects/ha/config docker compose up -d homeassistant ```