Maniacs_Mansion/NestQuest
11
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

release: make the 0.7.0 rollback instructions API-host-aware

Browse Source 
The API service owns and migrates the database at NESTQUEST_DB_PATH on the
API host; back up and restore it there, and scope the HACS/manual steps to
the Home Assistant integration component only.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
overseer
2026-09-24 00:14:42 -04:00
co-authored by Claude Opus 5.5
parent 4b80fffe67
commit 7969c164c4
1 changed files with 25 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files
RELEASE_NOTES.md
+25 -12
View File
@@ -83,22 +83,35 @@ Seventh release of NestQuest, promoting the admin surface from `dev` onto
**Schema version advances 7 → 8.** Migration 8 is additive, but a migrated **Schema version advances 7 → 8.** Migration 8 is additive, but a migrated
database **cannot** be read by 0.6.0 or earlier (they refuse a newer schema database **cannot** be read by 0.6.0 or earlier (they refuse a newer schema
version). **Back up `nestquest.db` (plus `-wal`/`-shm`) before upgrading.** To version). The database is owned and migrated by the **NestQuest API service**,
return to 0.6.0 you must restore that backup; a plain downgrade is impossible not by Home Assistant: it is the file at the API's configured
once migrated. `NESTQUEST_DB_PATH` on the API host, which need not be anywhere near the Home
Assistant config directory. To return to 0.6.0 you must restore a backup of
that file taken before the upgrade; a plain downgrade is impossible once
migrated.
**HACS installs:** **API host (database):**
1. Before upgrading, stop HA and back up `nestquest.db` (plus `-wal`/`-shm`) 1. Before upgrading, stop the NestQuest API service and back up the database
from the HA config directory. file at its configured `NESTQUEST_DB_PATH`, plus its `-wal` and `-shm`
2. To roll back: HACS > Integrations > NestQuest > Redownload > 0.6.0, restore sidecars (`<NESTQUEST_DB_PATH>-wal`, `<NESTQUEST_DB_PATH>-shm`) if present.
the backed-up database, restart Home Assistant. Only then deploy 0.7.0 and start the API service, which applies migration 8.
2. To roll back: stop the API service, restore the backed-up database and
sidecars to `NESTQUEST_DB_PATH`, redeploy the API service at 0.6.0, and roll
back the Home Assistant integration to 0.6.0 (below). Then restart the API
service and Home Assistant.
**Manual installs:** **Home Assistant integration — HACS installs** (integration component only;
the database lives with the API, see above):
1. Back up `nestquest.db` (plus `-wal`/`-shm`) before upgrading. 1. To roll back: HACS > Integrations > NestQuest > Redownload > 0.6.0, then
2. To roll back: replace `custom_components/nestquest/` with the 0.6.0 tree, restart Home Assistant.
restore the backed-up database, restart Home Assistant.
**Home Assistant integration — Manual installs** (integration component only;
the database lives with the API, see above):
1. To roll back: replace `custom_components/nestquest/` with the 0.6.0 tree,
then restart Home Assistant.
**Repository operators:** git-revert the 0.7.0 release merge on `main`. **Repository operators:** git-revert the 0.7.0 release merge on `main`.